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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Jul 31 2001 - 21:00:43 EST