mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Phil Endecott" <phil_wueww_endecott@chezphil.org>
To: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Script to build-in used modules, based on streamline_config.pl
Date: Sat, 18 Oct 2008 17:21:05 +0100	[thread overview]
Message-ID: <1224346865059@dmwebmail.dmwebmail.chezphil.org> (raw)

Dear List,

Last month, Steven Rostedt posted a script to disable 
not-currently-used modules from your .config:

   http://article.gmane.org/gmane.linux.kernel/734536

It works by parsing the kernel Makefiles to build a map from module 
names to config settings.

I've made a slightly modified version of this that takes the .config 
for an all-modular kernel (e.g. a distribution kernel) and changes the 
settings for those modules that are currently loaded so that they will 
be built in:

   http://chezphil.org/tmp/buildin_used_mods.pl

The aim of this is to provide a semi-automatic method to produce a 
custom kernel that has everything needed for your hardware built in, so 
you don't need an initrd.

One issue that I encountered is that not every config setting builds a 
module and may not be changed.  For example, if I need module xyz to 
support my IDE disk, then the script will change CONFIG_XYZ from m to 
y.  However, it won't change CONFIG_IDE from m to y.  When I 
subsequently make menuconfig, it detects that CONFIG_XYZ=y is 
incompatible with CONFIG_IDE=m, but it fixes it in the wrong way; it 
changes CONFIG_XYZ back to m, rather than changing CONFIG_IDE to y.  Is 
there any way to change this?

Someone with better Perl skills than me could probably merge Steven's 
original script with my variation with a command-line option to 
determine the behaviour.  It would be good to something like this merged.

Cheers,  Phil.




                 reply	other threads:[~2008-10-18 16:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1224346865059@dmwebmail.dmwebmail.chezphil.org \
    --to=phil_wueww_endecott@chezphil.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

all inboxes | Powered by JetHome®