Re: [Qemu-devel] Re: [PATCHv2 0/8 RFC] boot order specification

[Gleb Natapov]

On Thu, Nov 04, 2010 at 10:24:45AM +0100, Markus Armbruster wrote:
> Gleb Natapov <address@hidden> writes:
> 
> > On Sun, Oct 31, 2010 at 06:25:53PM -0400, Kevin O'Connor wrote:
> >> On Sun, Oct 31, 2010 at 01:40:01PM +0200, Gleb Natapov wrote:
> >> > This is current sate of the patch series for people to comment on.
> >> > I tried to use open firmware naming scheme to specify device path names.
> >> > 
> >> > The patch series produce names like these:
> >> > for pci machine:
> >> > /address@hidden/address@hidden/address@hidden/address@hidden
> >> > /address@hidden/address@hidden/address@hidden/address@hidden
> >> > /address@hidden/address@hidden,1/address@hidden:0
> >> > /address@hidden/address@hidden,1/address@hidden:1
> >> > /address@hidden/address@hidden/address@hidden
> >> > /address@hidden/address@hidden/address@hidden
> >> > /address@hidden/address@hidden/address@hidden
> >> > 
> >> > for isa machine:
> >> > adding '/isa/address@hidden/address@hidden' at index 2
> >> > adding '/isa/address@hidden/address@hidden' at index 1
> >> > adding '/isa/address@hidden/address@hidden:0' at index 0
> >> > adding '/isa/address@hidden/address@hidden:1' at index 3
> >> 
> >> Hi Gleb,
> >> 
> >> How will USB drives be identified?
> >> 
> > USB bus has Open Firmware binding. I haven't look at the spec yet, but it
> > should be easy.
> >
> >> I'm not sure how SeaBIOS will be able to line up something like
> >> "/address@hidden/address@hidden/address@hidden" to an optionrom BEV.  
> >> Also, if
> >> there is an optionrom with BCVs (eg, a scsi card), I'm not sure how
> >> that would that would be identified.
> >
> > The way to parse  "/address@hidden/address@hidden/address@hidden" is this: 
> > each
> > element (between /.../) consist of address@hidden node-name
> > describes device/bus. unit-address is a device address on preceding node.
> > So address@hidden tells us that this is pci bus accessible through io
> > register 0x0cf8, address@hidden tells us that this is ethernet device in pci
> > slot 4 function 0, (address@hidden,1 means ata device in slot 1 function 1).
> 
> Aren't "ethernet" and "ata" redundant there?
> 
In case of PCI bus yes. If parent bus does not allow to query device
type they are not.

--
                        Gleb.