• The_Decryptor@aussie.zone
    link
    fedilink
    English
    arrow-up
    6
    ·
    1 day ago

    I think x86 is basically the only platform that’s used ACPI, other hardware usually ships a fixed hardware list in firmware that the bootloader/kernel can read (Since it’s not like the motherboards are modular, e.g. the RTC is never going to randomly be connected to a different controller)

    Historically ARM didn’t even do that, it was mostly used in tightly linked systems so you’d just build those assumptions into the software itself (e.g. a Gameboy always has a directional pad on specific pins, so you just read those pins directly) I remember the early days of the Raspberry Pi involved device dependent kernel images because they had to code the specific initialisation routines into the drivers, it took a while for them to gain “device tree” support so you could have a generic kernel.

    • notanapple@lemm.ee
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 day ago

      I think x86 is basically the only platform that’s used ACPI

      ARM and x86. From wikipedia:

      Revision 5.0 of the ACPI specification was released in December 2011,[15] which added the ARM architecture support.

      • The_Decryptor@aussie.zone
        link
        fedilink
        English
        arrow-up
        3
        ·
        23 hours ago

        2011? That’s basically last week right?

        Support for it (and UEFI ) came with their push into servers, they were forced to make the platform a lot less special and more general purpose like x86 traditionally has been.

        End user facing hardware is a different matter though, like I know you can boot the Raspberry Pi via UEFI/ACPI (It builds the ACPI tables in the bootloader), but then Apple doesn’t use it at all for their ARM hardware and it uses something closer to a modern OpenFirmware.