Re: [ANNOUNCE] hotplug-ng 001 release

Erik van Konijnenburg
2005-02-11T22:07:24Z

On Fri, Feb 11, 2005 at 01:49:57PM -0800, Greg KH wrote:
> On Fri, Feb 11, 2005 at 10:37:31PM +0100, Erik van Konijnenburg wrote:
> > On Fri, Feb 11, 2005 at 11:23:23AM -0800, Greg KH wrote:
> > > On Fri, Feb 11, 2005 at 12:01:54PM -0700, Erik Andersen wrote:
> > > > On Fri Feb 11, 2005 at 09:01:44AM -0800, Greg KH wrote:
> > > > > It's not only pci, but all types of busses need this kind of "coldplug"
> > > > > functionality. And yes, I have plans to provide that functionality in
> > > > > this package too.
> > > > >
> > > > > In fact, if anyone looking to contribute some well defined and easy to
> > > > > test code... :)
> > > >
> > > > The pcimodules patch to pciutils does this sortof coldplug device
> > > > scanning for pci devices:
> > > > http://www.linuxfromscratch.org/patches/downloads/pciutils/pciutils-2.1.11-pcimodules-1.patch
> > >
> > > Yes, but that uses the modules.pcimap files, which we want to get rid of
> > > someday. It also uses the /proc/pci interface instead of sysfs, so it
> > > probably doesn't handle machines with pci domains very well...
> >
> > Could you give pointers to the "get rid of modules.pcimap" discussion?
>
> Search linux-kernel for it. It's come up many times between me and
> Rusty Russell. He's basically waiting for the hotplug scripts (or
> whatever) to be fixed up enough to not need them anymore.
>
> Do you have some other need for them?

Yep, I'm working on a proof of concept to show how modules.pcimap
can be used to build a more reliable mkinitrd. The interesting part about
modules.pcimap is that it can not only describe what's in the running
kernel, but also what's in the kernel about to be installed.

For an old version of the idea, see

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=284294

Regards,
Erik