From: Marcus Meissner <mm@ns.caldera.de>
To: thierry@cri74.org (Thierry Laronde), linux-kernel@vger.kernel.org
Subject: Re: [PCI] building PCI IDs/drivers DB from Linux kernel sources
Date: Mon, 30 Jul 2001 13:03:01 +0200 [thread overview]
Message-ID: <200107301103.f6UB31e20045@ns.caldera.de> (raw)
In-Reply-To: <20010730113319.A24939@pc04.cri.cur-archamps.fr>
In article <20010730113319.A24939@pc04.cri.cur-archamps.fr> you wrote:
> Please note that in the following, these are remarks _not_ bad criticism.
> Maybe what is found by the script could be of some interest to people
> coordinating the source writing.
> GOAL
> ----
> 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
> I have decided to write a script (you will find all the stuff attached)
> parsing the Linux kernel sources in order to do that.
Well, that was what I did 2 years ago for Caldera ;)
Howevery this is no longer needed.
Nearly all PCI kernel modules now export the ids they match for in the
MODULE_DEVICE_TABLE, for PCI, ISAPNP and USB.
So either read it from /lib/modules/<kernelver>/modules.*map, or
use the modutils code that extracts this information from the
.o files itself.
You need to compile those, but you usually do that anyway for a kernel
build.
Ciao, Marcus
next prev parent reply other threads:[~2001-07-30 11:03 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 [this message]
2001-07-30 11:22 ` Thierry Laronde
2001-07-30 11:06 ` Keith Owens
2001-07-30 11:20 ` Thierry Laronde
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=200107301103.f6UB31e20045@ns.caldera.de \
--to=mm@ns.caldera.de \
--cc=linux-kernel@vger.kernel.org \
--cc=thierry@cri74.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