@hrw @ryan @ariadne @mjg59 I’m aware of a rack mounted cluster of 16 to 20 BeagleBoards. It’s possible that a certain swedish troll was aware of this beagle cluster but if I had to guess it the predates 2014

@karolherbst it was open sourced (bsd 3 clause) at the end of last year. This reminds me that I wanted to build it and benchmark asahi.

@karolherbst the account suggesting the DMCA takedown in the issue is a coding agent according to its github profile page

@mgorny behavior matches expectation based on the nick name. Translation executor (of wills) but with alternate meaning of executioner, i.e. exceutor of a death sentence

@siguza I don’t use Filevault on my asahi test devices but the default scaling on a 13-inch 1920x1080 is annoying. Just thought this week that it would be nice if the display was lying about it size.

@trini there is a script (https://github.com/AsahiLinux/m1n1/blob/main/proxyclient/tools/linux.py) for m1n1's proxy mode which uploads kernel, initramfs and optionally u-boot and boots them.
When using u-boot the script modifies the embedded default environment to boot kernel and initramfs from the known memory addresses. See the script source starting at line 84.
This worked with the distro boot scripts since it replaced the complex boot script as that is not necessary. This broke with bootstd as the default environment is tiny and there is not much which can be dropped.
I probably got overboard with the 8K padding but one intended use case is https://gitlab.freedesktop.org/gfx-ci/boot2container and I wasn't sure how long the boot arguments for that can get. I started looking how to solve this for upstream u-boot.
One option I thought of is using `... char default_environment[CONFIG_ENV_DEFAULT_ENV_EMBEDDED_SIZE] = {` with CONFIG_ENV_DEFAULT_ENV_EMBEDDED_SIZE unset by default. The other one is to let the build system append a configurable sized padding at the end.