[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 3/4] Stellaris machine config

From: Markus Armbruster
Subject: Re: [Qemu-devel] [PATCH 3/4] Stellaris machine config
Date: Fri, 12 Jun 2009 15:56:05 +0200
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (gnu/linux)

Gerd Hoffmann <address@hidden> writes:

>> I guess FDT is missing a "#include" equivalent, and possibly name
>> constants.
> See:
> http://git.jdl.com/gitweb/?p=dtc.git;a=blob;f=Documentation/manual.txt;h=f8a8a7b482e3a2a1501614c94fa0ea87aeb3a9e7;hb=HEAD
> There is:
> /include/ "filename"
>> But for QEMU, some way to give names to, say, a standard SoC or a
>> basic board, or a PC without peripherals, and then refer to them in
>> another FDT tree, would be useful.
> Yes, that must be solved somehow.  Just punting the issue to the vm
> management software isn't acceptable IMHO.
> I'm not sure includes will solve that issue.  What we need is more a
> tree merge, i.e. you could have basic config files for a few pc
> variants without devices (i.e. isapc, pc) and config files snippets
> for devices (ide interface foo, sound card bar, ...).  Then you need
> some way to merge the latter into the former.
> Even that solves only a part of the problem.  For some options you
> effectively have to edit the device tree:
> -m <mem>
>   You have edit address@hidden node.  You even might have to add a node
>   depending on the amount of memory (i.e. one for the memory below
>   4G one for the memory above ...).
> -cpu <cpu>
>   You have to edit the cpu node.
> -smp <n>
>   You have to insert cpu nodes.
> cheers,
>   Gerd

For what it's worth, that's how my prototype worked.  Start with a
minimal, fixed tree for the machine type, then edit it according to

reply via email to

[Prev in Thread] Current Thread [Next in Thread]