From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Any ETA on getting the PCI hardware detection event replaying
Date: Mon, 05 Feb 2001 03:02:29 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98140527721202@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98124426910212@msgid-missing>
There's a bit in CVS right now, relying on versions of
Adam Richter's "pcimodules". The USB analogue will
require usbdevfs and "usbmodules" ... that's for the quick
solution using off-the-shelf components.
There's an issue there: how to get the related programs
properly up-to-date. "pcimodules" is a patch to "pciutils"
now (I'd like a change in it, details below), and the
current "usbutils" release is missing the modutils 2.4.2
support patch. I don't see getting rid of the need for
hotplug awareness in such utilities, unless more data shows
up in /proc and it gets easier to parse without C code.
- Dave
p.s. "pcimodules" changes I'd like to see:
- "-s pci_slot_name" ... one function at a time. On
big systems, the current version might touch
hundreds of PCI busses (said LKML recently)
- "--version" ... so scripts can defend against
versions that are old or buggy
- "--if-unbound" (or somesuch) ... don't bother
saying anything if the function has a driver
already. (/proc/bus/pci/devices has that info.)
----- Original Message -----
From: "Miles Lane" <miles@megapathdsl.net>
To: <linux-hotplug-devel@lists.sourceforge.net>
Sent: Saturday, February 03, 2001 3:53 PM
Subject: Any ETA on getting the PCI hardware detection event replaying added?
>
> Hi,
>
> It seems like concensus has been reached about the general
> requirements for handling the detection of PCI/Cardbus devices
> which are already plugged in at boot time (this is the problem
> where exec_usermodehelper + /sbin/hotplug can't handle device
> detection and module insertion early in the boot sequence).
> I'm wondering if anyone is currently working on implementing
> this.
>
> Miles
>
> _______________________________________________
> Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
> Linux-hotplug-devel@lists.sourceforge.net
> http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2001-02-05 3:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-03 23:53 Any ETA on getting the PCI hardware detection event replaying added? Miles Lane
2001-02-05 3:02 ` David Brownell [this message]
2001-02-05 22:50 ` Any ETA on getting the PCI hardware detection event replaying David Brownell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-hotplug-98140527721202@msgid-missing \
--to=david-b@pacbell.net \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.