From: Pete Zaitcev <zaitcev@redhat.com>
To: chriswhite@gentoo.org
Cc: zaitcev@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: Kernel Driver Automation
Date: Wed, 16 Feb 2005 13:59:10 -0800 [thread overview]
Message-ID: <20050216135910.1873a672@localhost.localdomain> (raw)
In-Reply-To: <mailman.1108494546.30588.linux-kernel2news@redhat.com>
On Wed, 16 Feb 2005 04:05:47 +0900, Chris White <chriswhite@gentoo.org> wrote:
> Ironically, if the network card driver is not working, there's no way to
> google around for information on what modules to compile in for various
> drivers. [...]
I always google for the PCI IDs which lspci -n shows.
> The basic idea would be to have a userspace program that would be run
> before the kernel compile process and check the device identification
> string (using /proc?) and match it up against the correct module. [...]
We already do have such a program, it's called /sbin/hotplug. The missing
piece for your scheme, however, is that the maps which govern hotplug are
generated from C files. Therefore, the code is patched to add new IDs.
AFAIK, Greg Kroah worked on a more configurable way to match drivers with
devices within the hotplug framework. You might want to talk to Greg
about this.
By the way, Greg is a Gentoo developer as well, but pleas keep this to
a common forum. I'm sure folks from other distros are be interested.
Jaa ne,
-- Pete
next parent reply other threads:[~2005-02-16 21:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1108494546.30588.linux-kernel2news@redhat.com>
2005-02-16 21:59 ` Pete Zaitcev [this message]
2005-02-15 19:05 Kernel Driver Automation Chris White
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=20050216135910.1873a672@localhost.localdomain \
--to=zaitcev@redhat.com \
--cc=chriswhite@gentoo.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox