> Date: Mon, 20 Jan 2025 10:25:49 +0900
> From: FUKAUMI Naoki <na...@radxa.com>

Hi Naoki,

> Hi Mark,
> 
> On 1/20/25 00:27, Mark Kettenis wrote:
> >> Date: Sun, 19 Jan 2025 12:35:59 +0900
> >> From: FUKAUMI Naoki <na...@radxa.com>
> > 
> > Hello,
> > 
> >> Hi,
> >>
> >> I'm trying to boot OpenBSD/arm64 on a Radxa Orion O6.
> >>
> >> UEFI has a "O/S Hardware Description Selection" menu where I can choose
> >> "Device Tree" or "ACPI". "ACPI" allows me to boot a mainline Linux kernel.
> >>
> >> With "ACPI" I can use the serial console with efiboot, but the kernel
> >> output only shows up on the display after the kernel is loaded.
> > 
> > To support the serial console in "ACPI" mode, an SPCR table is needed.
> > Probably something that should be enabled in your EDK II build.
> 
> It looks like the SPCR is compiled and built in, but I'm not familiar 
> with EDK II...

The OpenBSD bootloader prints the list of ACPI tables and SPCR isn't
printed in the screenshot you made.  It might be built in, but not
enabled.  There might be an option in the EDK II firmware setup menu
to enable serial console redirection.

> At least the serial console works under mainline Linux in ACPI mode.

Linux might be looking at the DBG2 table, which is present.  OpenBSD
doesn't look at that yet.  But I'm looking into that now.  If the
Orion O6 board is primarily targeted at people building some sort of
desktop machine rather than a server, it might actually make sense to
only provide DBG2 and not SPCR.  Such a configuration would indicate
that the framebuffer should be the default output choice, but that a
serial port is available for debug output.  The OpenBSD implementation
I'm considering is that one could switch to serial console in this
case by typing something like "set tty com0" at the boot> prompt.

> >> Here is a screenshot on the display:
> >>    
> >> https://drive.google.com/file/d/1EIrQO3qxl9F6AQO5y5mzeTleTbDauRqm/view?usp=sharing
> > 
> > Does it hang at that point?
> > 
> >> Using "Device Tree" I was able to see the kernel panic occur using the
> >> serial console (please see below).
> > 
> > Does the device tree have a #redistributor-regions property that is
> > set to a number larger than one?
> 
> I have included additional information in my previous email. Please 
> check it out.

Looks like indeed #redistributor-regions is 12 in your device tree.
I'm implementing support for that, but it'll take me a few days to
finish that and test it properly.  I'll let you know when that's done.

Cheers,

Mark

Reply via email to