all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: Herman Rimm <herman@rimm.ee>, 70131@debbugs.gnu.org
Cc: vagrant@debian.org, Efraim Flashner <efraim@flashner.co.il>
Subject: [bug#70131] [PATCH v3 0/6] Update U-Boot.
Date: Tue, 17 Dec 2024 16:04:44 -0800	[thread overview]
Message-ID: <87ed25g8kj.fsf@contorta> (raw)
In-Reply-To: <87h672exxx.fsf@contorta>

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

On 2024-12-17, Vagrant Cascadian wrote:
> On 2024-12-17, Vagrant Cascadian wrote:
>> I just did some basic boot testing of u-boot-pinebook and
>> u-boot-rock64-rk3328, by manually installing and booting Debian with it,
>> though I have not tested with Guix System (and not sure I will be able
>> to).
>>
>> I might be able to test u-boot-sifive-unmatched next. Having troubles
>> unrelated to these patches with the rockpro64 board, but hope to get
>> those fixed.
>
> Boot tested u-boot-rockpro64-rk3399 booting Debian. So that is three
> targets not fundamentally broken, at least. :)

And also boot tested u-boot-sifive-unmatched, which had a glitch in how
it changed the boot device order and booted an old kernel from a device
that the previous defaults did not boot... so that is a bit
odd... worked around it by renaming the extlinux.conf file so that it
would not select it.

Other platforms that switched from u-boot's distro boot to u-boot's
bootstd might have similar issues, so it is something to note possibly
in a news entry.

This might be worth setting BOOTSTD_FULL=y in the configuration; without
it there is no way to select the boot device if the first one it picks
is not the one you actually want... and possibly trying to get that
upstream too.


live well,
  vagrant

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

  reply	other threads:[~2024-12-18  0:06 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-01 20:20 [bug#70131] [PATCH 0/5] Add bootloaders and update U-Boot Herman Rimm via Guix-patches via
2024-04-01 20:22 ` [bug#70131] [PATCH 1/5] gnu: bootloader: Add nanopi-r4s-rk3399 bootloader Herman Rimm via Guix-patches via
2024-04-01 20:22 ` [bug#70131] [PATCH 2/5] gnu: u-boot: Use DDR3 patch for Nano Pi R4S Herman Rimm via Guix-patches via
2024-04-01 20:22 ` [bug#70131] [PATCH 3/5] gnu: firmware: Update make-arm-trusted-firmware to 2.10 Herman Rimm via Guix-patches via
2024-04-01 20:22 ` [bug#70131] [PATCH 4/5] gnu: u-boot: Update to 2024.04-rc5 Herman Rimm via Guix-patches via
2024-04-01 20:22 ` [bug#70131] [PATCH 5/5] gnu: bootloader: Add orangepi-zero2w bootloader Herman Rimm via Guix-patches via
2024-05-09  5:35 ` [bug#70131] [PATCH 0/5] Update U-boot Herman Rimm via Guix-patches via
2024-05-09  5:35   ` [bug#70131] [PATCH 1/5] gnu: bootloader: Add nanopi-r4s-rk3399 bootloader Herman Rimm via Guix-patches via
2024-05-09  5:35   ` [bug#70131] [PATCH 2/5] gnu: u-boot: Use DDR3 patch for Nano Pi R4S Herman Rimm via Guix-patches via
2024-05-15 18:16     ` Vagrant Cascadian
2024-05-09  5:35   ` [bug#70131] [PATCH 3/5] gnu: firmware: Update make-arm-trusted-firmware to 2.10 Herman Rimm via Guix-patches via
2024-05-09  5:35   ` [bug#70131] [PATCH 4/5] gnu: u-boot: Update to 2024.04 Herman Rimm via Guix-patches via
2024-05-09  5:35   ` [bug#70131] [PATCH 5/5] gnu: bootloader: Add orangepi-zero2w bootloader Herman Rimm via Guix-patches via
2024-05-15 20:26   ` [bug#70131] [PATCH 0/5] Update U-boot Vagrant Cascadian
2024-05-16  7:28     ` Herman Rimm via Guix-patches via
2024-05-16 15:56       ` Vagrant Cascadian
2024-08-26 14:45 ` [bug#70131] [PATCH v2 1/8] gnu: bootloader: Add nanopi-r4s-rk3399 bootloader Herman Rimm via Guix-patches via
2024-08-26 14:45   ` [bug#70131] [PATCH v2 2/8] gnu: u-boot: Use DDR3 patch for Nano Pi R4S Herman Rimm via Guix-patches via
2024-08-26 14:45   ` [bug#70131] [PATCH v2 3/8] gnu: firmware: Update make-arm-trusted-firmware to 2.10 Herman Rimm via Guix-patches via
2024-08-26 14:45   ` [bug#70131] [PATCH v2 4/8] gnu: u-boot: Update to 2024.07 Herman Rimm via Guix-patches via
2024-08-26 14:45   ` [bug#70131] [PATCH v2 5/8] gnu: python-u-boot-pylib: Fix pyproject.toml Herman Rimm via Guix-patches via
2024-08-26 14:45   ` [bug#70131] [PATCH v2 6/8] gnu: u-boot-rockpro64-rk3399: Unconfigure CONFIG_DM_SCSI Herman Rimm via Guix-patches via
2024-08-26 14:45   ` [bug#70131] [PATCH v2 7/8] gnu: u-boot-sandbox: Unconfigure CONFIG_RSA and CONFIG_TOOLS_LIBCRYPTO Herman Rimm via Guix-patches via
2024-08-26 14:45   ` [bug#70131] [PATCH v2 8/8] gnu: bootloader: Add orangepi-zero2w bootloader Herman Rimm via Guix-patches via
2024-12-13 19:58 ` [bug#70131] [PATCH v3 0/6] Update U-Boot Herman Rimm via Guix-patches via
2024-12-13 19:58   ` [bug#70131] [PATCH v3 1/6] Revert "gnu: u-boot-tools: Fix segfault while running tests." Herman Rimm via Guix-patches via
2024-12-13 19:58   ` [bug#70131] [PATCH v3 2/6] gnu: u-boot: Update to 2024.10 Herman Rimm via Guix-patches via
2024-12-13 19:58   ` [bug#70131] [PATCH v3 3/6] gnu: u-boot-tools: Remove extraneous native-input Herman Rimm via Guix-patches via
2024-12-13 19:58   ` [bug#70131] [PATCH v3 4/6] gnu: u-boot: Use search-patches Herman Rimm via Guix-patches via
2024-12-13 19:58   ` [bug#70131] [PATCH v3 5/6] gnu: bootloaders: u-boot-sandbox: Reformat Herman Rimm via Guix-patches via
2024-12-13 19:58   ` [bug#70131] [PATCH v3 6/6] gnu: u-boot: Use guix-name Herman Rimm via Guix-patches via
2024-12-15  8:46     ` Vagrant Cascadian
2024-12-15  9:20   ` [bug#70131] [PATCH v3 0/6] Update U-Boot Vagrant Cascadian
2024-12-17 22:04     ` Vagrant Cascadian
2024-12-17 22:39       ` Vagrant Cascadian
2024-12-18  0:04         ` Vagrant Cascadian [this message]
2024-12-18 23:25   ` bug#70131: " Vagrant Cascadian

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=87ed25g8kj.fsf@contorta \
    --to=vagrant@debian.org \
    --cc=70131@debbugs.gnu.org \
    --cc=efraim@flashner.co.il \
    --cc=herman@rimm.ee \
    /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.