Re: adding UEFI to NetBSD /boot/ [was Re: no HDMI on rpi4b NetBSD 10.1]

[Steve Rikli <sr%genyosha.net@localhost>]

On Thu, Jul 17, 2025 at 05:17:38PM +0200, Martin Husemann wrote:
> On Thu, Jul 17, 2025 at 08:10:24AM -0700, Steve Rikli wrote:
> 
> > I figured I was stuck using UEFI to select console, after I saw
> > 'consdev' wasn't available from the boot loader:
> 
> Yeah, that was only "fixed" for amd64 very recentish, but since with
> evbarm the firmware usually offers a sane way to configure serial / dual
> console, there is no pressing need to force things like on amd64 (where
> only "server class" machines usually offer some kind of serial support).

Understood. My (mostly older) PC's (i386 and amd64) all have serial ports,
NUCs and Lenovo M9xx series too, so the ones with NetBSD make use of
/boot.cfg for console setup, at least. My preferred method. :-)

> So overall: I would stick with the UEFI configuration options for
> console, but you can use boot.cfg to e.g. boot kernels from a different
> partition, with a different name, or force root on some other partition/
> device.

OK. After being resolved to using UEFI for console selection, I was
slightly surprised /boot/cmdline.txt didn't have more effect, since
arm64.img cmdline.txt comes with "console=fb", I'd hoped it would be as
simple as changing fb to com0. Unfortunately that didn't work.

Knowing that bootaa64.efi handles that helps my understanding.

Thanks,
sr.