From: "Roland" <devzero@web.de>
To: "\"Alex Bennee\"" <kernel-hacker@bennee.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Calculating CONFIG's from lsmod info
Date: Sat, 27 Dec 2008 15:27:08 +0100 [thread overview]
Message-ID: <001001c9682f$33186c40$6602a8c0@bui.materna.com> (raw)
Maybe http://cateee.net/autokernconf/ is worth to take a look at.....
roland
List: linux-kernel
Subject: Calculating CONFIG's from lsmod info
From: "Alex Bennee" <kernel-hacker () bennee ! com>
Date: 2008-12-27 11:31:01
Message-ID: b2cdc9f30812270331g3435e0b1wb28573c4e6782e9 () mail ! gmail !
com
[Download message RAW]
Hi,
Following a conversation with my Dad concerning his new netbook we
discussed one option for speeding up the boot process was a static
kernel with the correct config for his actual hardware, obviating the
need for initrd and the rest of the flexible hardware hackery. However he
has
less patience than me for reading through each Kconfig entry so I'm
wondering if it's possible to come up with a solution that just works
(tm).
Given we usually know the config of the running kernel
(/proc/config.gz or some package copy of it) and the modules that have
been successfully loaded (lsmod) it must be deducible which CONFIG_*
to turn from m to y for a kernel rebuild.
The info from modinfo brings up a host of information for each module
but the CONFIG flag that selects it for building is not one of them.
Is there some sort of macro magic that could add the flag as module
information or will I be reduced to grokking Makefile to deduce which
object was invoked by which switch?
Or am I in fact re-inventing a wheel that has already been created
but isn't living in the scripts directory?
--
Alex, homepage: http://www.bennee.com/~alex/
CV: http://www.bennee.com/~alex/cv.php
next reply other threads:[~2008-12-27 14:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-27 14:27 Roland [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-27 11:31 Alex Bennee
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='001001c9682f$33186c40$6602a8c0@bui.materna.com' \
--to=devzero@web.de \
--cc=kernel-hacker@bennee.com \
--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
all inboxes | Powered by JetHome®