On Fri, Sep 06, 2024 at 02:00:57PM -0600, Simon Glass wrote: > Hi Patrick, > > On Fri, 6 Sept 2024 at 01:22, Patrick Rudolph > <[email protected]> wrote: > > > > Based on the existing work done by Simon Glass this series adds > > support for booting aarch64 devices using ACPI only. > > As first target QEMU SBSA support is added, which relies on ACPI > > only to boot an OS. As secondary target the Raspberry Pi4 was used, > > which is broadly available and allows easy testing of the proposed > > solution. > > > > The series is split into ACPI cleanups and code movements, adding > > Arm specific ACPI tables and finally SoC and mainboard related > > changes to boot a Linux on the QEMU SBSA and RPi4. Currently only the > > mandatory ACPI tables are supported, allowing to boot into Linux > > without errors. > > > > The QEMU SBSA support is feature complete and provides the same > > functionality as the EDK2 implementation. > > > > The changes were tested on real hardware as well on QEMU v9.0: > > > > qemu-system-aarch64 -machine sbsa-ref -nographic -cpu cortex-a57 \ > > -pflash secure-world.rom \ > > -pflash unsecure-world.rom > > > > qemu-system-aarch64 -machine raspi4b -kernel u-boot.bin -cpu cortex-a72 \ > > -smp 4 -m 2G -drive file=raspbian.img,format=raw,index=0 \ > > -dtb bcm2711-rpi-4-b.dtb -nographic > > > > Please note that the current implementation still requires a DTB to be > > The word 'still' suggests that it won't one day. But U-Boot uses > devicetree for its configuration so this will always be the case. I > suggest removing 'still'.
Pointing over at x86 where we have dts files, yes, please remove the word "still" and perhaps otherwise reword a few things. U-Boot is happy to pass along ACPI and so forth to the OS, but will continue using device tree internally. -- Tom
signature.asc
Description: PGP signature
