Hi Gleb, On Tue, Nov 23, 2010 at 05:31:41PM +0200, Gleb Natapov wrote: > Anthony, Blue > > No comments on this patch series for almost a week. Can it be applied? My apologies - I haven't had time to review. > On Wed, Nov 17, 2010 at 06:43:47PM +0200, Gleb Natapov wrote: > > I am using open firmware naming scheme to specify device path names. > > In this version: added SCSI bus support. Pass boot order list as file > > to firmware. > > > > Names look like this on pci machine: [...] > > /pci@i0cf8/usb@1,2/hub@1/network@0/ethernet@0 > > /rom@genroms/linuxboot.bin What's the plan for handling optionroms (ie, BCVs and BEVs)? This is an area which is a bit tricky - mainly due to legacy BIOS crud. An option rom can register either a BEV (eg, gpxe on a network card), or it can register one or more BCVs (eg, a scsi card registering two drives). How do we say boot from the optionrom on the second nic card? If you have a scsi card, how do we communicate that its second drive should be the c: drive? The ugly thing about BCVs is that they are not necessarily registered in the rom for the device that controls it. So, if you have two of the same type of scsi card, each with two drives, it's possible for the optionrom to put all four drives in the rom of the first scsi card. > > Gleb Natapov (16): [...] > > Pass boot device list to firmware. It looks like you went with a newline separated list. Thanks. -Kevin -- 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
