[Qemu-devel] Re: [PATCHv3 00/14] boot order specification

[Blue Swirl]

On Thu, Nov 11, 2010 at 10:21 AM, Gerd Hoffmann <address@hidden> wrote:
> On 11/10/10 18:14, Gleb Natapov wrote:
>>
>> This is current sate of the patch series for people to comment on.
>> I am using open firmware naming scheme to specify device path names.
>>
>> Names look like this on pci machine:
>> /address@hidden/address@hidden,1/address@hidden/address@hidden
>> /address@hidden/address@hidden/address@hidden/address@hidden
>> /address@hidden/address@hidden/address@hidden/address@hidden
>> /address@hidden/address@hidden,1/address@hidden/address@hidden
>> /address@hidden/address@hidden,1/address@hidden/address@hidden
>> /address@hidden/address@hidden/address@hidden
>> /address@hidden/address@hidden/address@hidden
>> /address@hidden/address@hidden/address@hidden
>> /address@hidden/address@hidden,1/address@hidden/address@hidden
>> /address@hidden/address@hidden/address@hidden/address@hidden/address@hidden
>> /address@hidden/address@hidden,2/address@hidden/address@hidden
>> /address@hidden/address@hidden,2/address@hidden/address@hidden/address@hidden
>
> Good stuff overall, but see replies to patches for some nits.
>
> IIRC some powerpc (+sparc?) boards pass a device tree to the guest.  So with
> this (and maybe some more bits) we might be able to dynamically generate a
> device tree from our qdev tree?  Any comments from the ppc/sparc folks on
> this?

Sparc does not use the device tree in real life, except a binary
machine description is used by Sun4v hypervisor. But using a device
tree could simplify how OpenBIOS (for both Sparc and PPC) supports
different machine types.

Device tree is already used by for example Bamboo (PPC) and Petalogix
(Microblaze) boards.