2 ms·
All RISC-V consumer boards running Linux also use DT. RISC-V is also working on getting ACPI but primarily for the sake of servers, just like with ARM where ACP
by Arnavion 1y ago
All RISC-V consumer boards running Linux also use DT. RISC-V is also working on getting ACPI but primarily for the sake of servers, just like with ARM where ACPI is primarily used for servers (ARM SBBR / ServerReady).
ARM Windows laptops only use ACPI because Windows has no interest in DTs, but under Linux these devices are still booted using DT. I don't know for sure, but the usual reason is that these ACPI implementations are hacked up by the manufacturer to be good enough to work with Windows, so supporting them on Linux requires more effort than just writing up the DT.
- ChocolateGod 1y ago> so supporting them on Linux requires more effort than just writing up the DT. More effort then producing unique images for every board?
- Arnavion 1y agoYes. See https://github.com/aarch64-laptops/edk2/tree/dtbloader-app?tab=readme-ov-file#why-not-acpi https://github.com/aarch64-laptops/edk2/tree/dtbloader-app?t... for example.
- ChocolateGod 1y agoIt's a shame the DT approach encourages land fill of boards when the manufacturer stops providing updates.
- Arnavion 1y agoNot necessarily. DT can be loaded separately from u-boot tree / kernel tree / dtoverlay file.
- mappu 1y agoThe DT should really be put in the firmware (e.g u-boot), same as ACPI on x86 is in the firmware (the bios/efi). Then you wouldn't need a unique kernel/OS image. For devices that have u-boot in ROM the DT is usually there (fdt).