From: Thierry Laronde <thierry@cri74.org>
To: Keith Owens <kaos@ocs.com.au>
Cc: Debian boot mailing list <debian-boot@lists.debian.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PCI] building PCI IDs/drivers DB from Linux kernel sources
Date: Mon, 30 Jul 2001 13:20:13 +0200 [thread overview]
Message-ID: <20010730132013.C25441@pc04.cri.cur-archamps.fr> (raw)
In-Reply-To: <20010730113319.A24939@pc04.cri.cur-archamps.fr> <22966.996491181@ocs3.ocs-net>
In-Reply-To: <22966.996491181@ocs3.ocs-net>; from kaos@ocs.com.au on Mon, Jul 30, 2001 at 09:06:21PM +1000
On Mon, Jul 30, 2001 at 09:06:21PM +1000, Keith Owens wrote:
> On Mon, 30 Jul 2001 11:33:19 +0200,
> Thierry Laronde <thierry@cri74.org> wrote:
> >In order to allow a kind of light detection of hardware to be use during
> >installation, I wanted to build a database (for PCI: I start with the
> >easiest...) with the following format:
> >
> >CLASS_ID VENDOR_ID DEVICE_ID driver_name
>
> depmod already builds /lib/modules/`uname -r`/modules.pcimap containing
> all the data required for PCI identification. Before you reinvent too
> many wheels, see the hotplug project,
> http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
Thanks for the pointer. I will give a look.
--
Thierry LARONDE, Centre de Ressources Informatiques, Archamps - France
http://www.cri74.org/
next prev parent reply other threads:[~2001-07-30 11:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-30 9:33 [PCI] building PCI IDs/drivers DB from Linux kernel sources Thierry Laronde
2001-07-30 10:11 ` Tim Waugh
2001-07-30 11:03 ` Marcus Meissner
2001-07-30 11:22 ` Thierry Laronde
2001-07-30 11:06 ` Keith Owens
2001-07-30 11:20 ` Thierry Laronde [this message]
2001-07-30 19:30 ` Glenn
2001-08-07 22:51 ` Eric Van Buggenhaut
-- strict thread matches above, loose matches on Subject: below --
2001-07-30 10:04 Giacomo Catenazzi
2001-07-30 10:10 ` Thierry Laronde
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=20010730132013.C25441@pc04.cri.cur-archamps.fr \
--to=thierry@cri74.org \
--cc=debian-boot@lists.debian.org \
--cc=kaos@ocs.com.au \
--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