On Thu, Nov 11, 2010 at 10:21 AM, Gerd Hoffmann <kra...@redhat.com> 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: >> /p...@i0cf8/i...@1,1/dr...@1/d...@0 >> /p...@i0cf8/i...@1/f...@03f1/flo...@1 >> /p...@i0cf8/i...@1/f...@03f1/flo...@0 >> /p...@i0cf8/i...@1,1/dr...@1/d...@1 >> /p...@i0cf8/i...@1,1/dr...@0/d...@0 >> /p...@i0cf8/s...@3/d...@0 >> /p...@i0cf8/ether...@4/ethernet-...@0 >> /p...@i0cf8/ether...@5/ethernet-...@0 >> /p...@i0cf8/i...@1,1/dr...@0/d...@1 >> /p...@i0cf8/i...@1/i...@01e8/dr...@0/d...@0 >> /p...@i0cf8/u...@1,2/netw...@0/ether...@0 >> /p...@i0cf8/u...@1,2/h...@1/netw...@0/ether...@0 > > 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.
