Maybe a dumb question but how do non x86 boards normally boot Linux images in a generic way? When I was in the embedded space, our boards all relied on very specific device tree blobs. Is the same strategy used for these or does it use ACPI or something?
Arnavion|9 months ago
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|9 months ago
More effort then producing unique images for every board?
rwmj|9 months ago
jabl|9 months ago
ARM servers do the same with SBSA (a spec that mandates things like UEFI, ACPI etc. support) etc. I think there's some effort in RISC-V land to do the same, also using UEFI and ACPI.
skywal_l|9 months ago
[0] Supervisor Binary Interface
IshKebab|9 months ago
beeflet|9 months ago
Arnavion|9 months ago
ChocolateGod|9 months ago
pantalaimon|9 months ago