From: Efraim Flashner <efraim@flashner.co.il>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: custom kernel config
Date: Wed, 3 Apr 2019 22:04:04 +0300 [thread overview]
Message-ID: <20190403190404.GB1203@macbook41> (raw)
In-Reply-To: <87wokb1pg1.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1719 bytes --]
On Wed, Apr 03, 2019 at 01:08:14AM -0700, Chris Marusich wrote:
> Efraim Flashner <efraim@flashner.co.il> writes:
>
> > I'm playing around with the idea of creating a custom kernel
>
> Cool! I'm curious to know how you're passing the custom config in. Are
> you using the #:extra-options keyword argument of the make-linux-libre
> procedure? Are you passing in a procedure to generate the entire custom
> configuration via the #:configuration-file keyword argument? Something
> else?
>
For the first one I used the #:extra-options route and compiled a list.
The second one I tried I created a custom kernel and left #:defconfig as
#f and inherited that to add a kconfig to the native-inputs.
Once I read a bit more of the kernel documentation it wasn't too bad to
create a list of what I needed.
tar xf $(guix build linux-libre -S)
cd linux-libre<tab>
touch .config
guix environment linux-libre
make localmodconfig
copy that into .config and fix the formatting
make localmodconfig
if that works well enough then add "CONFIG_MODULES=y" to .config and
you're ready to try it out. Stock kernel on my slow desktop took 243(?)
minutes, the custom kernel from localmodconfig took 21 minutes, but I
haven't tested it yet.
When I try again on my laptop I'm going to go again with #:extra-options
since I can define the localmodconfig options as
%macbook41-kernel-options and append to it other groups of modules, such
as filesystems, efi support, etc.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-04-03 19:04 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 18:04 custom kernel config Efraim Flashner
2019-04-01 18:30 ` Pierre Neidhardt
2019-04-02 5:37 ` Efraim Flashner
2019-04-02 8:04 ` Pierre Neidhardt
2019-04-02 14:49 ` Efraim Flashner
2019-04-01 19:46 ` Ludovic Courtès
2019-04-02 14:50 ` Efraim Flashner
2019-04-03 8:08 ` Chris Marusich
2019-04-03 19:04 ` Efraim Flashner [this message]
2019-04-03 19:49 ` Pierre Neidhardt
2019-04-03 20:27 ` Efraim Flashner
2019-04-04 8:44 ` Chris Marusich
2019-04-07 14:36 ` Efraim Flashner
2019-04-07 17:25 ` Pierre Neidhardt
2019-04-08 14:52 ` Ludovic Courtès
2019-04-08 15:03 ` Pierre Neidhardt
2019-05-01 7:54 ` Pierre Neidhardt
2019-05-06 3:46 ` Chris Marusich
2019-05-06 8:01 ` Efraim Flashner
2019-05-06 8:34 ` Pierre Neidhardt
2019-05-01 9:31 ` Mark H Weaver
2019-05-01 14:15 ` Ludovic Courtès
2019-05-15 18:09 ` [BLOG] " Efraim Flashner
2019-05-16 11:10 ` Pierre Neidhardt
2019-05-16 19:15 ` Efraim Flashner
2019-05-16 11:48 ` Pierre Neidhardt
2019-05-16 14:29 ` Marius Bakke
2019-05-16 14:33 ` Pierre Neidhardt
2019-05-16 19:14 ` Efraim Flashner
2019-05-17 0:15 ` Mark H Weaver
2019-05-17 7:50 ` Efraim Flashner
2019-05-20 14:57 ` Ludovic Courtès
2019-05-20 17:38 ` Efraim Flashner
2019-05-21 10:07 ` Ludovic Courtès
2019-05-21 12:46 ` zimoun
2019-05-18 2:04 ` ison
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=20190403190404.GB1203@macbook41 \
--to=efraim@flashner.co.il \
--cc=cmmarusich@gmail.com \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.