From: Richard Sent <richard@freakingpenguin.com>
To: 55909@debbugs.gnu.org
Subject: bug#55909: Converging aux-files/linux-libre/* towards mainline defconfigs
Date: Thu, 23 May 2024 15:03:44 -0400 [thread overview]
Message-ID: <87jzjkuz8v.fsf@freakingpenguin.com> (raw)
In-Reply-To: <87o7yze19b.fsf@tom-fitzhenry.me.uk>
I would be in favor of building more initrd modules into the kernel when
done so upstream. To my understanding the distinction between
linux-libre and linux-libre-*-generic is to have both:
a) A kernel with options that support the various Guix services OOTB,
such as CONFIG_BINFMT_MISC and qemu-binfmt-service-type.
b) A kernel that matches upstream defconfigs as much as possible, with
the exception of a subset of flags considered essential. See
%default-extra-linux-options or linux-libre-riscv64-generic.
With this model, linux-libre should avoid diverging from upstream
defconfigs whenever possible, particularly when toggling a module from y
to m. linux-libre would become a superset of *-generic kernels.
Obviously I'm not packaging linux-libre myself. I might misunderstand
the purpose of these variants. :)
On a related note, the *-generic kernels seem to also have encapsulated
"add support for a specific board on this platform", which to me feels a
bit like a hacky solution. See linux-libre-arm64-generic and the
Pinebook Pro comments. I'd think that would belong in a
linux-libre-pinebook-pro or similar.
--
Take it easy,
Richard Sent
Making my computer weirder one commit at a time.
prev parent reply other threads:[~2024-05-23 19:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-11 14:13 bug#55909: linux-libre-arm64-generic with %base-initrd-module => kernel module not found "ahci" Tom Fitzhenry
2024-05-23 19:03 ` Richard Sent [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87jzjkuz8v.fsf@freakingpenguin.com \
--to=richard@freakingpenguin.com \
--cc=55909@debbugs.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).