unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: romulasry <romulasry@protonmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Default to the 5.7.X kernel by default
Date: Fri, 12 Jun 2020 13:29:14 +0200	[thread overview]
Message-ID: <87wo4cttdh.fsf@nckx> (raw)
In-Reply-To: <7f64UTd060zhbC_QWiknReo6nDDJ29meyFRwCXbSb6sysoYULGg1-qBgLHxgIyk_nuRTfTobKt1cDwpFSqW_KHrhXKzUPhQwUkJy25lHErk=@protonmail.com>

[-- Attachment #1: Type: text/plain, Size: 992 bytes --]

Romulas,

romulasry 写道:
> Would that be a good idea or not?

We're less in need of ideas than volunteers.  There are 5.7 
Linux-Libre kernels already in Guix to support specific ARM 
devices, but the 5.7 kernel configuration hasn't been vetted to 
the same FSDG standards as the 5.4 series from which it diverged. 
This would need to be done for all supported architectures, in 
addition to regular ‘does it boot’ testing.

To get started, you simply copy 
gnu/packages/aux-files/linux-libre/5.4-$ARCH.conf to <kernel 
sources>/.config, then run ‘make oldconfig’.  Then you diff the 
new configuration file against the 5.4, since more will have 
changed than only what you entered interactively.  Then you make 
sure each option makes sense for a generic distribution kernel 
following the FSDG.

I'd close with ‘help wanted’ (and I will!), but this requires 
familiarity with the kernel, the FSDG, and of course Guix.  Still,

Help wanted,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2020-06-12 11:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-11 22:02 Default to the 5.7.X kernel by default romulasry
2020-06-12 11:29 ` Tobias Geerinckx-Rice [this message]
2020-06-12 11:57   ` Tobias Geerinckx-Rice

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=87wo4cttdh.fsf@nckx \
    --to=me@tobias.gr \
    --cc=guix-devel@gnu.org \
    --cc=romulasry@protonmail.com \
    /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).