From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Enzo Desiage <enzo@desiage.org>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: .config
Date: Fri, 21 Feb 2020 19:15:33 -0500 [thread overview]
Message-ID: <125650.1582330533@turing-police> (raw)
In-Reply-To: <CAJwv8c2ngQq-BEWQB_gxe9AFszz07aGLZoi3Kjm1SxRCRnpv9Q@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 817 bytes --]
On Fri, 21 Feb 2020 23:41:10 +0000, Enzo Desiage said:
> modules I actually need (thanks find_all_modules.sh). I'm trying to devise
> a strategy to take the output of that script and make a brand new minimal
> .config file. However, the only solution I've found is doing it manually
> via make menuconfig. This seems to be a rather long process, which I
> wouldn't mind doing if there aren't any other alternatives.
> Is there any other way?
Step 1: Plug in all your USB widgets and storage and other hot-pluggables
long enough for the kernel to load each device's drivers.
Step 2: 'make localmodconfig'. This will create a .config that only has those
modules that were actually loaded at the time (there's also an option to take
the output of an 'lsmod', in case you're doing the builds on a different machine)
[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2020-02-22 0:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 23:41 .config Enzo Desiage
2020-02-22 0:15 ` Valdis Klētnieks [this message]
2020-02-22 17:39 ` .config Enzo Desiage
2020-02-22 22:47 ` .config Valdis Klētnieks
2020-02-23 3:54 ` .config Aruna Hewapathirane
2020-02-23 6:47 ` .config Pratyush Das
2020-02-23 12:18 ` .config Bjørn Mork
2020-02-23 7:31 ` .config Greg KH
2020-02-23 16:29 ` .config Enzo Desiage
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=125650.1582330533@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=enzo@desiage.org \
--cc=kernelnewbies@kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.