Re: [RFC 00/12] RFC: Devicetree-ACPI hybrid mode

[Bryan O'Donoghue <bod@kernel.org>]

On 23/06/2026 15:52, Hans de Goede wrote:
> Comments, thoughts ?

Throw out DT and just do this...

One thing I like about this approach TBH is that you don't do the easy 
thing of presuming to push the hard work into the bootloader - thus 
creating a dependency on bootloader.

We've had _alot_ of problems doing DT selectivity to get OSes installed 
on arm64 laptops. You mentioned I2C-HID devices and EC controllers which 
I agree are a good and obvious targets.

I don't think this can replace a full and complete DT but, then I don't 
think that should be the objective.

Much like installing cursed OSes like Windows on "normal" laptops or x86 
machines, you'd expect to boot in ACPI mode have enough of the OS 
running to install more of the OS - which I think _can_ be a viable 
objective with an ACPI-DT translator.

Sadly OpenBSD could boot all the way to console on the Qcom laptops 
where Linux could not - because ACPI support was better there.

And, we have Nvidia laptops coming too, Windows laptops which will parse 
ACPI tables to boot.

There's almost no upside in having ACPI data and not trying to make 
maximal use of it, especially if you don't have a DT supplied by 
antecedent boot stages.

---
bod