On Thu, Nov 11, 2010 at 10:21 AM, Gerd Hoffmann <kraxel@xxxxxxxxxx> 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: >> /pci@i0cf8/ide@1,1/drive@1/disk@0 >> /pci@i0cf8/isa@1/fdc@03f1/floppy@1 >> /pci@i0cf8/isa@1/fdc@03f1/floppy@0 >> /pci@i0cf8/ide@1,1/drive@1/disk@1 >> /pci@i0cf8/ide@1,1/drive@0/disk@0 >> /pci@i0cf8/scsi@3/disk@0 >> /pci@i0cf8/ethernet@4/ethernet-phy@0 >> /pci@i0cf8/ethernet@5/ethernet-phy@0 >> /pci@i0cf8/ide@1,1/drive@0/disk@1 >> /pci@i0cf8/isa@1/ide@01e8/drive@0/disk@0 >> /pci@i0cf8/usb@1,2/network@0/ethernet@0 >> /pci@i0cf8/usb@1,2/hub@1/network@0/ethernet@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. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
