unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: raingloom <raingloom@riseup.net>
To: "Jonathan Marsden" <jmarsden@fastmail.fm>
Cc: help-guix@gnu.org
Subject: EDK2 support Was: Another Raspberry Pi data point
Date: Fri, 12 Feb 2021 06:12:27 +0100	[thread overview]
Message-ID: <20210212061227.02ee5558@riseup.net> (raw)
In-Reply-To: <2774b71b-0865-4fd4-b9c9-2beabd0e6b7a@www.fastmail.com>

On Thu, 11 Feb 2021 19:24:36 -0600
"Jonathan Marsden" <jmarsden@fastmail.fm> wrote:

> As I understand it, aarch64 SBCs each have their own different, not
> yet standardized, boot processes, so unlike common x86-64 "PC"
> machines, there is a need for boot definition work that is
> board-specific.

There is actually a standard-ish way: UEFI.
I've had some luck using EDK2 on my RPi 3 B+, but only with a third
party binary. It could indeed boot generic aarch64 Debian.
My channel has an old experimental and broken description of it, but
the licensing of the modules necessary to build EDK2 for the Pi3
specifically is unclear to me. Certainly some nonfree assets there, but
I'm not sure if they are all absolutely necessary, or if they are
actually binaries or just nonfree source code.

Channel:
https://git.sr.ht/~raingloom/guix-packages

Look in the raingloom/packages/bootloaders.scm


  parent reply	other threads:[~2021-02-12  5:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-10 21:06 Another Raspberry Pi data point Richard Huxton
2021-02-11  2:14 ` Leo Famulari
2021-02-11  4:34   ` Jonathan Marsden
2021-02-11 21:21     ` Leo Famulari
2021-02-12  1:24       ` Jonathan Marsden
2021-02-12  2:19         ` Vagrant Cascadian
2021-02-12  5:12         ` raingloom [this message]
2021-02-15 10:02         ` Efraim Flashner
2021-02-15 10:06           ` Efraim Flashner

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=20210212061227.02ee5558@riseup.net \
    --to=raingloom@riseup.net \
    --cc=help-guix@gnu.org \
    --cc=jmarsden@fastmail.fm \
    /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.
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).