From: Roman Shaposhnik <roman@shaposhnik.org>
To: 9front@9front.org
Subject: Re: [9front] UEFI boot on ARM / RPi
Date: Thu, 21 May 2020 19:14:34 -0700 [thread overview]
Message-ID: <CA+ULb+ttkW0fxFM3nvgSNEEUu_Z0Twj2vQwJjmi46dzVFGPFPg@mail.gmail.com> (raw)
In-Reply-To: <20200522015137.34db73fc@riseup.net>
On Thu, May 21, 2020 at 4:51 PM raingloom <raingloom@riseup.net> wrote:
> Hi folks!
>
> So, I recently found out about EDK2 for Raspberry Pi
WFWI, you now have eve more choice with UEFI payloads on RPi:
https://github.com/ARM-software/u-boot/blob/master/doc/README.uefi
I am actually using that (and so does SuSE for example)
> and since I had
> plenty of issues trying to boot from my external HDD connected via USB,
> and this seems to solve it, at least for kernels that support UEFI,
> which 9front does not.
>
> My question is, obviously, could someone help add support for it? As I
> understand it, it would also help booting on other ARM platforms that
> have UEFI support.
My immediate question is around build tooling: UEFI presupposes that
you're producing a PE/COFF binary from your build toolchain. On Linux
you do with things like linker scripts, not sure what a native Plan9
equivalent would be.
Thanks,
Roman.
next prev parent reply other threads:[~2020-05-22 2:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 23:51 raingloom
2020-05-22 2:14 ` Roman Shaposhnik [this message]
2020-05-22 2:29 ` [9front] " ori
2020-05-22 8:23 ` hiro
2020-05-22 15:16 ` raingloom
2020-05-22 16:58 ` hiro
2020-05-22 22:44 ` raingloom
2020-05-22 22:52 ` Daniel Morandini
2020-05-23 3:34 ` raingloom
2020-05-23 7:34 ` hiro
2020-05-23 19:20 ` John Weaver
2020-05-22 10:59 ` cinap_lenrek
2020-05-25 3:14 ` Roman Shaposhnik
2020-05-25 6:49 ` cinap_lenrek
2020-05-23 23:13 ` Ethan Gardener
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+ULb+ttkW0fxFM3nvgSNEEUu_Z0Twj2vQwJjmi46dzVFGPFPg@mail.gmail.com \
--to=roman@shaposhnik.org \
--cc=9front@9front.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.
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 NNTP newsgroup(s).