unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Dariqq <dariqq@posteo.net>
To: Leo Famulari <leo@famulari.name>
Cc: Wilko Meyer <w@wmeyer.eu>, 74757@debbugs.gnu.org
Subject: [bug#74757] [PATCH 0/3] Linux-libre updates (2024-12-09)
Date: Sun, 15 Dec 2024 09:23:46 +0000	[thread overview]
Message-ID: <c5f12e01-2627-4172-86da-003ad272d68e@posteo.net> (raw)
In-Reply-To: <Z1esesLY9RV3HNVH@jasmine.lan>

Hi Leo,

Apologies for the rather late response.

On 10.12.24 03:50, Leo Famulari wrote:
> On Mon, Dec 09, 2024 at 09:38:27PM +0000, Dariqq wrote:
>> Hello,
>>
>> Here are the updates for linux-libre from 2024-12-05 and 2024-12-09.
> 
> Thank you! I pushed these patches to the 'kernel-updates' branch to
> build them and make it easy to test them.
> 
> https://ci.guix.gnu.org/eval/1892282
> https://ci.guix.gnu.org/jobset/kernel-updates
> 
>> The 6.11 and the 4.19 series are now marked as EOL on kernel.org and should be removed soon.
> 
> Noted! The end of the 4s... crazy.
> 
>> Haven't tried to get 6.12 packaged yet. Are there instructions for updating the config files?
> 
> Basically, check out the source code of the kernel you want to build.
> Find the most recent Guix config file that corresponds to the system
> type and kernel release series that you want to build for. Copy it into
> the root of the kernel source tree as '.config'. Make the kernel
> dependencies available with `guix shell -D linux-libre` and then run
> `make ARCH=$systemtype oldconfig`.
> 
> We build kernels for systems of these types:
> arm <- 32-bit ARM, called "armhf" in Guix
> arm64 <- called "aarch64" in Guix
> i386 <- 32-bit Intel compatible, called "i686" in Guix
> riscv
> amd64 <-64-bit Intel compatible, called "x86_64" in Guix
> 
> And the config files are located in the Guix source tree under
> 'gnu/packages/aux-files/linux-libre'.
> 
> In general, we aim to make the kernels support whatever hardware you
> throw at them. Distro kernels are big! But there's some judgement and
> personal choice involved too. Like, it's unlikely that anyone will use
> 32-bit ARM Guix on a Rockchip SBC and then use it to run some industrial
> device in a factory. And if they do, they can build their own kernel or
> ask us to enable the driver.
> 
> If you've never configured the build of the kernel, it asks you a series
> of questions about features and drivers to support. I use my judgment,
> read online documentation about the options, and ask on #guix IRC or
> similar places for advice. Guix kernels are supposed to be
> fully-featured, not minimal.
> 
> I like this site for information about the options:
> 
> https://cateee.net/lkddb/web-lkddb/HSA_AMD.html
> 
> I had thought about tackling 6.12 next weekend. But I'm happy for you to
> try it, and I can help you too if you like. Please let me know what you
> think about trying this.

It seems a lot more complicated than I initally thought . Not sure if I 
want to go down the rabbit hole of kernel configuration.




      parent reply	other threads:[~2024-12-15  9:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-09 21:38 [bug#74757] [PATCH 0/3] Linux-libre updates (2024-12-09) Dariqq
2024-12-09 21:40 ` [bug#74757] [PATCH 1/3] gnu: linux-libre 6.11: Update to 6.11.11 Dariqq
2024-12-09 21:40 ` [bug#74757] [PATCH 2/3] gnu: linux-libre 6.6: Update to 6.6.64 Dariqq
2024-12-09 21:40 ` [bug#74757] [PATCH 3/3] gnu: linux-libre-4.19: Update to 4.19.325 Dariqq
2024-12-10  2:50 ` [bug#74757] [PATCH 0/3] Linux-libre updates (2024-12-09) Leo Famulari
2024-12-11  0:56   ` bug#74757: " Leo Famulari
2024-12-15  9:23   ` Dariqq [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=c5f12e01-2627-4172-86da-003ad272d68e@posteo.net \
    --to=dariqq@posteo.net \
    --cc=74757@debbugs.gnu.org \
    --cc=leo@famulari.name \
    --cc=w@wmeyer.eu \
    /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).