Ludovic Courtès writes:
> It went from 17.1% to 17.3% in two days, even though the AArch64
> machines have been busy all along it seems. Maybe they’ve been
> processing the backlog that had accumulated on ‘master’ rather than the
> things we care about.
Per https://issues.guix.gnu.org/55848, i
Per https://ci.guix.gnu.org/eval/364633?status=pending , there are ~5k
scheduled jobs, all aarch64-linux.
Per https://ci.guix.gnu.org/workers, all workers report being idle.
Thus, it looks like the aarch64 builders have stalled.
On Thu, 5 May 2022, at 2:14 AM, Vagrant Cascadian wrote:
> You could create a "generic" image that supports UEFI or standard u-boot
> methods, and the user can bring-their-own UEFI implementation
> (e.g. tianocore, recent versions of u-boot with EFI) or install u-boot
> or barebox or whatever manua
ttps://tow-boot.org/devices/index.htmlcommit 397ee4242238905c8c1071aff6d345c600a709d6
Author: Tom Fitzhenry
Date: Mon Apr 25 16:51:52 2022 +1000
add rockpro64 image
diff --git a/gnu/system/images/rockpro64.scm b/gnu/system/images/rockpro64.scm
new file mode 100644
index 00..d03b4b90d
