From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mimir.eigenstate.org ([206.124.132.107]) by ewsd; Thu May 21 22:30:04 EDT 2020
Received: from abbatoir.fios-router.home (pool-162-83-132-245.nycmny.fios.verizon.net [162.83.132.245])
	by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id e981a6e8 (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO);
	Thu, 21 May 2020 19:29:49 -0700 (PDT)
Message-ID: <D754294E49DA1BF02580EE969E6C1D70@eigenstate.org>
To: roman@shaposhnik.org, 9front@9front.org
Subject: Re: [9front] UEFI boot on ARM / RPi
Date: Thu, 21 May 2020 19:29:47 -0700
From: ori@eigenstate.org
In-Reply-To: <CA+ULb+ttkW0fxFM3nvgSNEEUu_Z0Twj2vQwJjmi46dzVFGPFPg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: converged HTTP metadata firewall 

> 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.

We support that in 8l for UEFI boot support: take a look at '-3' or '-4'.
You'd need to teach the appropriate arm linker about this too.