From: Alexander Mieland <dma147@linux-stats.org>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: how to find out which module was built by which .config variables?
Date: Fri, 3 Mar 2006 14:39:20 +0100 [thread overview]
Message-ID: <200603031439.24367.dma147@linux-stats.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0603031434520.2581@yvahk01.tjqt.qr>
[-- Attachment #1: Type: text/plain, Size: 1468 bytes --]
Am Friday 03 March 2006 14:35 schrieben Sie:
> >Hello,
> >
> >I need to create a database with configuration options (the ones
> >in .config) and the resulting kernel modules.
>
> Let's pick 8139too.ko for example.
> Find /usr/src/linux -name 8139too.ko
> In that same directory, look at the Makefile:
> obj-$(CONFIG_8139TOO) += 8139too.o
Ahh, great, this helps much more!
Thanks. ;)
> >Is there any simple possibility (with bash and its applications) to
> > find out, which kernel modules will be built by which .config options?
> > I know that there are also many dependencies between the options and
> > the modules and I want to add them to the database too. The
> > dependencies can be found out with the Kconfig files, I think.
> >
> >I've already looked into the source files of some modules, but I can
> > not find any commonalities which would make it easy to find the
> > module-name which will be build.
> >
> >I've found some stuff like this:
> >#define DRIVER_NAME "8139too"
> >or things linke:
> >#define <something>_MODULES_NAME "some string which seems to be the
> >descriptive name"
> >
> >But this doesn't really help... :(
--
Alexander 'dma147' Mieland 2.6.15-ck3-r1-fb-my4 SMP
FnuPG-ID: 27491179 Registered Linux-User #249600
http://blog.linux-stats.org http://www.linux-stats.org
http://www.mieland-programming.de http://www.php-programs.de
[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2006-03-03 13:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 13:20 how to find out which module was built by which .config variables? Alexander Mieland
2006-03-03 13:35 ` Jan Engelhardt
2006-03-03 13:39 ` Alexander Mieland [this message]
2006-03-03 14:04 ` Steven Rostedt
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=200603031439.24367.dma147@linux-stats.org \
--to=dma147@linux-stats.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