On Sat, 15 Mar 2025 11:49:14 +0100
Simon Josefsson via "Development of GNU Guix and the GNU System
distribution." <guix-devel@gnu.org> wrote:

> +  (bootloader (bootloader-configuration
> +               ;; Due to FSDG issues with the DDR training binaries,
> we cannot
> +               ;; currently ship u-boot in guix:
> +
> ;; 
> https://www.collabora.com/news-and-blog/blog/2024/02/21/almost-a-fully-open-source-boot-chain-for-rockchips-rk3588/
> +               ;; Defining an empty bootloader generates an
> extlinux.conf that
> +               ;; nearly any modern u-boot can read.
> +              (bootloader u-boot-bootloader)))
Thanks a lot for this trick (that could be handy with
u-boot-qemu-arm64).

> I assume something must have written the non-free u-boot blob to
> internal flash memory or sdcard?  Is it necessary to re-run 'guix
> system reconfigure' to re-create the extlinux.conf for Guix after
> that external process rewrote the u-boot blob, or how would the
> entire workflow look like?
Another option could be to tell the system configuration to only ship
GRUB and have u-boot provided by either mnt-reform or another project
load that GRUB.

This worked with the Pinephone with TowBoot when I tested few years ago.

Though I'm unsure if it would work in all cases since there is a
bug where GRUB requires the same block size (like 512 bytes / 4KiB)
between the filesystem and the block device.

Denis.

Attachment: pgpSmY7XOU5wy.pgp
Description: OpenPGP digital signature

Reply via email to