qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [PATCH 0/5] boot order specification


From: Gleb Natapov
Subject: Re: [Qemu-devel] [PATCH 0/5] boot order specification
Date: Tue, 26 Oct 2010 17:43:13 +0200

On Tue, Oct 26, 2010 at 03:35:38PM +0000, Blue Swirl wrote:
> On Tue, Oct 26, 2010 at 10:48 AM, Gleb Natapov <address@hidden> wrote:
> > This is current sate of the patch series for people to comment on.
> > I dropped ioport double reservation checking from isa-bus and added
> > bus_id field for IDE bus since as Markus pointed out unit has different
> > meaning there.
> >
> > This patch series produce names like:
> >
> > address@hidden,03f7/address@hidden
> > address@hidden,03f7/address@hidden
> > address@hidden:00:01.1/address@hidden:0
> > address@hidden:00:01.1/address@hidden:1
> > address@hidden:00:03.0/address@hidden
> > address@hidden:00:04.0/address@hidden
> >
> > They will be passed to BIOS to determine boot order.
> 
> We also use OpenBIOS for PPC and Sparcs. A compatible boot device for
> those would be OpenFirmware tree name. I think your names should then
> become:
> /pci/isa/address@hidden/address@hidden
> /pci/isa/address@hidden/address@hidden
Why is it PCI?

> /pci/address@hidden/1,0
> /pci/address@hidden/1,1
Where pci address here?

> /pci/address@hidden
> /pci/address@hidden
And here?

And we will need to describe ROMs too. I planned to have something like:
address@hidden for roms loaded with -option-rom command line option.

> 
> The PCI addressing scheme in OF was a bit twisty, I just invented
> integers in place of those.
> 
> Anyway, I don't think we should invent yet another device path naming system.
IS this format documented somewhere? I am not attached to specific
format at all.

--
                        Gleb.



reply via email to

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