Re: [PATCHv4 15/15] Pass boot device list to firmware.

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

 



On Tue, Nov 16, 2010 at 06:30:19PM +0000, Blue Swirl wrote:
> >> Perhaps the FW path should use device class names if no name is specified.
> > What do you mean by "device class name". We can do something like this:
> > if (dev->child_bus.lh_first)
> >        return dev->child_bus.lh_first->info->name;
> >
> > i.e if there is child bus use its bus name as fw name. This will make
> > all pci devices to have "pci" as fw name automatically. The problem is
> > that theoretically same device can provide different buses.
> 
> I meant PCI class name, like "display" for display controllers,
> "network" for NICs etc.
> 
That is what my pci bus related patch is doing already.

> >> I'll try Sparc32 to see how this fits there.
> 
> Except bootindex is not implemented for SCSI.
Will look into adding it.

--
			Gleb.
--
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


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux