On Mon, 25 Sep 2000, Dan Hollis wrote:
> On Mon, 25 Sep 2000, Jeff Garzik wrote:
> > I see you suggestion in the same way... If we keep the PCI device name
> > data around after boot, then we have a lot of kernel memory locked up
> > on the off chance that a HotPlug PCI device might appear for which we
> > need a name.
> > I would much prefer a userspace solution for naming unnamed PCI devices
> > after boot...
> How about the kernel calling lspci?
Kernel calling a proggie is no problem... CONFIG_KMOD does it, and Linus
has suggest that hotplugging a device needs to fire off a script, like
/sbin/hotplug-net eth0 # new eth0 just inserted
If hotplugging executes an action, then updating the PCI device name
should become part of that. That implies that the kernel won't do any
of the executing... /sbin/hotplug-net will initiate the device name
update, so the kernel needs a way to update the device name at the
request of userspace. It could be something as simple as
echo name > /proc/bus/pci/00/0a.0/name
or something more complex...
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Sep 30 2000 - 21:00:14 EST