Vagrant Cascadian <vagr...@debian.org> writes: > On 2025-03-13, Vagrant Cascadian wrote: >> Just pushed a "wip-linux-libre-arm64-mnt-reform" branch that contains a >> kernel for the MNT/Reform family of systems. >> >> I have successfully built and booted a linux-libre-arm64-mnt-reform@6.12 >> kernel on a "MNT Reform2 with RCORE RK3588 Module" ... running Debian, I >> know... but Guix System cannot be too far off! > > Not far off at all, turns out! Pushed an example config to the > wip-linux-libre-arm64-mnt-reform branch!
Wow, this is really nice. So that means 'guix system reconfigure' on that machine would work? What must be done to the machine before this part would work: + (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))) 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? /Simon
signature.asc
Description: PGP signature
