Re: Automatic Configuration of a Kernel

Chris White
2005-09-15T00:24:30Z

[-- Attachment #1: Type: text/plain, Size: 1888 bytes --]

On Thursday 15 September 2005 09:09, Marek W wrote:
> On Thu, 15 Sep 2005 09:49, Daniel Thaler wrote:
> > Michal Piotrowski wrote:
> > > Hi,
> > >
> > > On 15/09/05, Ahmad Reza Cheraghi <a_r_cheraghi@yahoo.com> wrote:
> > >>Hi
> > >>
> > >>I wrote this Framework for making a .config based on
> > >>the System Hardwares. It would be a great help if some
> > >>people would give me their opinion about it.

[tons of snipping]

> Something that can do the hardware detection, then maps that to drivers
> would be very useful.

well, in theory this works as well. If you do this in the kernel source
directory:

make allmodconfig

that makes a kernel with all possible configure options that can be built as
modules enabled.

make install

and you have a couple of nice files in /lib/modules/(version)/modules.*map

-rw-r--r-- 1 root root 73 Sep 14 23:15 modules.ieee1394map
-rw-r--r-- 1 root root 132 Sep 14 23:15 modules.inputmap
-rw-r--r-- 1 root root 81 Sep 14 23:15 modules.isapnpmap
-rw-r--r-- 1 root root 7834 Sep 14 23:15 modules.pcimap
-rw-r--r-- 1 root root 43 Sep 14 23:15 modules.seriomap
-rw-r--r-- 1 root root 80010 Sep 14 23:15 modules.usbmap

the usual favorite of mine is modules.pcimap, which, when compined with lspci
can give you the proper module for your pci device. Granted it has the fault
of a) how to figure out the configure option. Sometimes it's CONFIG_[name],
sometimes it's not (grepping maybe?) b) sometimes two drivers do the same
thing, but if enabled together will cause kittens to cry and babies to pull
flowers. Therein lies one of the main issues. I'm going to assume by seeing
the rules_file bit that you address it in that way. However, seeing the
development model of the kernel, trying to keep that updated may get a little
weird.

My 1.5 $denomination
Chris White

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]