From: "Tom Fitzhenry" <tom@tom-fitzhenry.me.uk>
To: "Vagrant Cascadian" <vagrant@debian.org>,
"Tobias Platen" <guix@platen-software.de>,
guix-devel <guix-devel@gnu.org>
Subject: Re: Guix System on RockPro64
Date: Thu, 05 May 2022 12:48:57 +1000 [thread overview]
Message-ID: <8e5f7582-deb4-47ec-bb9e-101034979cf8@www.fastmail.com> (raw)
In-Reply-To: <87r159w9zj.fsf@contorta>
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 manually.
Yes, this is the idea behind Tow-Boot. Tow-Boot is an opinionated build of u-boot that implements enough of EFI to be able to boot a generic UEFI image.
The same image would work for any aarch64 device supporting EFI: via Tianocore, via Tow-Boot, via ARM BBR, ...
I intend to write this up in more detail with my patches.
> My understanding was tow-boot was mostly, at this point, something to
> avoid installing as part of the distro image. You can basically do the
> same thing with mainline u-boot, if you install u-boot to media other
> than the distro media. Or does tow-boot have fancier features working
> yet (e.g. menu interfaces from the firmware) ?
Yes, the distro is not responsible for installing Tow-Boot on the SPI. If a user's device doesn't support EFI, and they want to install Tow-Boot on SPI, they would need to do that themselves (by following Tow-Boot's installation instructions). PostmarketOS are working on delivering Tow-Boot updates via LVFS: https://github.com/fwupd/fwupd/issues/4294
The only thing Guix needs to do is provide a generic aarch64 image that supports UEFI. I have something WIP for that.
prev parent reply other threads:[~2022-05-05 3:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 18:53 Guix System on RockPro64 Tobias Platen
2022-05-04 12:34 ` Tom Fitzhenry
2022-05-04 16:14 ` Vagrant Cascadian
2022-05-05 2:48 ` Tom Fitzhenry [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8e5f7582-deb4-47ec-bb9e-101034979cf8@www.fastmail.com \
--to=tom@tom-fitzhenry.me.uk \
--cc=guix-devel@gnu.org \
--cc=guix@platen-software.de \
--cc=vagrant@debian.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).