From: Roman Shaposhnik <roman@shaposhnik.org>
To: 9front@9front.org
Subject: Re: [9front] UEFI boot on ARM / RPi
Date: Sun, 24 May 2020 20:14:14 -0700 [thread overview]
Message-ID: <CA+ULb+sQb78DejBGZY_vbFbubbKBik3Q9kQY5-mC5S21o32w5w@mail.gmail.com> (raw)
In-Reply-To: <5519AFF64A52D10C25545175AF3C1EE5@felloff.net>
On Fri, May 22, 2020 at 3:59 AM <cinap_lenrek@felloff.net> wrote:
>
> ... not using any of this in 9boot on 386/amd64 tho. just linking
> a headerless file (-H3) hand hand crafting the PE header in the
> assembler. with 6l, i'm even just generating a a.out and stripping
> off the a.out header with dd.
>
> see /sys/src/boot/efi/pe32.s and /sys/src/boot/efi/pe64.s
Thanks! This is very helpful.
Btw, I'm trying to setup a development environment for Plan9/Pi
and it seems that I can't make my qemu-system-aarch64 emulate
enough of a UART for 9pi3 kernel to be happy. E.g.
qemu-system-aarch64 -M raspi3 -kernel 9pi3 -append console=0
-serial mon:stdio
actually does the right thing and even brings up the GUI, but
it doesn't really seem to use the UART -- hence the console is empty.
If anybody has any hints as to where to dig to -- I'd appreciate it.
Thanks,
Roman.
next prev parent reply other threads:[~2020-05-25 3: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 ` [9front] " Roman Shaposhnik
2020-05-22 2:29 ` 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 [this message]
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+sQb78DejBGZY_vbFbubbKBik3Q9kQY5-mC5S21o32w5w@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).