unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: Leo Famulari <leo@famulari.name>, Wilko Meyer <w@wmeyer.eu>
Cc: 68988@debbugs.gnu.org, Tobias Geerinckx-Rice <me@tobias.gr>
Subject: bug#68988: All arm64/aarch64 platforms disabled in linux-libre 6.7.x!
Date: Wed, 21 Feb 2024 10:11:26 -0800	[thread overview]
Message-ID: <87bk893cxd.fsf@wireframe> (raw)
In-Reply-To: <ZcVvipjH8dWpednw@jasmine.lan>

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

On 2024-02-08, Leo Famulari wrote:
> On Thu, Feb 08, 2024 at 07:57:38AM +0100, Wilko Meyer wrote:
>> Vagrant Cascadian <vagrant@debian.org> writes:
>> > The linux-libre 6.7.x package contains ... as far as I can tell, no
>> > supported arm64/aarch64 platforms! This is a pretty significant
>> > regression from the linux-libre 6.6.x packaging!
>
> Huh!
>
> When I was generating configs, I never did anything very special to
> ensure continued aarch64 support in new kernel series except for `make
> ARCH=arm64 oldconfig`.

Maybe a stray typo, e.g. ARCH=amd64 vs. ARCH=arm64 ? Only one-letter
difference and a slight position shift ... easy to think one thing and
type another!

> It would be useful if others would help by testing the patches adding
> new kernel series on aarch64 or other non-x86_64 platforms. In my
> observation that rarely happens. And then bugs like this can slip in.

At any rate, I can confirm that it now works again on a virtualized
arm64 system! I can probably test this when introducing a new series if
given a heads-up.

I haven't yet tested other physical systems, but glancing
over the diff looks promising...

Thanks for the fix!


live well,
  vagrant

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

  reply	other threads:[~2024-02-21 18:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-08  2:12 bug#68988: All arm64/aarch64 platforms disabled in linux-libre 6.7.x! Vagrant Cascadian
2024-02-08  6:57 ` Wilko Meyer
2024-02-09  0:19   ` Leo Famulari
2024-02-21 18:11     ` Vagrant Cascadian [this message]
2024-02-09 20:28 ` bug#68988: [PATCH] gnu: linux-libre 6.7: Modify .conf files Wilko Meyer
2024-02-18 22:44   ` Leo Famulari
2024-02-20 17:14     ` Leo Famulari

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=87bk893cxd.fsf@wireframe \
    --to=vagrant@debian.org \
    --cc=68988@debbugs.gnu.org \
    --cc=leo@famulari.name \
    --cc=me@tobias.gr \
    --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).