• onlinepersona@programming.dev
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    1 day ago

    On regular x86 laptops, this mapping is already present in the UEFI firmware, described as ACPI tables. ACPI, which stands for Advanced Configuration and Power Interface, is an open standard that some firmware implementations use to advertise the devices that are part of the system to the operating system through a key-value data structure called “ACPI tables”. At boot, when the operating system detects ACPI tables, it reads them to enumerate the hardware devices and allow the various drivers and kernel modules to interact with all compatible discovered devices.

    Why doesn’t Quallcomm have this? Seems like a major oversight. Kinda weird that they don’t have ACPI. It’s an open standard…

    Anti Commercial-AI license

    • notanapple@lemm.ee
      link
      fedilink
      English
      arrow-up
      4
      ·
      edit-2
      20 hours ago

      ETA: Sorry I was wrong. ACPI doesnt solve this*. Arm SystemReady SR/ES does and its why Ampere cpus can boot on linux on release without too much work.

      Sadly its currently only used for iot/server stuff but hopefully it will eventually make its way to consumer tech. We need to raise awareness on this and pressure companies to commit to this standard.

      *From what I read, WoA has full ACPI support but qcoms ACPI apis only work on Windows. [1 (ms link)][2]

      Yeah its really unfortunate that most arm chips/devices use DTs instead of conforming to ACPI. However with ARM becoming more prominent on servers (and desktops), Im hoping this changes. There is now a push for ACPI on Arm since thats what companies running Arm on servers want. Ampere server cpus eg have ACPI support and arm now has docs on ACPI. I hope qualcomm is also forced to support ACPI. I think they will have to do it if they want to see their cpus being used in data centers and the like.