ACPIPRT(4)
π ACPIPRT(4) π
okay so this is from the Kernel Interfaces Manual, section 4 β it's acpiprt, and bestie, it's giving "quietly holding the whole system together" energy β¨
πΈ NAME πΈ
acpiprt β ACPI PCI routing table configuration. that's it, that's the whole vibe π
π¦ SYNOPSIS π¦
acpiprt* at acpi?
like, one line, zero drama, iconic behavior π
β¨ DESCRIPTION β¨
okay so listen π β the acpiprt driver is the one handing out interrupt mapping information for your PCI devices, and it gets all of that from the ACPI PCI Routing Table objects. no cap, that's literally its entire job π«Ά
typically there's one PCI Routing Table object for every PCI bus in the system, and each one of those gets handled by its own separate acpiprt device. so like, one bus β one object β one driver instance. it's a whole matching set, very coordinated, we love to see it π
ngl this is the kind of background work that nobody thanks but everybody needs π the main character energy is real.
π SEE ALSO π
go read those too, iykyk πβ¨
π HISTORY π
the acpiprt driver first appeared in OpenBSD 4.1 β a certified vintage icon at this point π°οΈπ
π AUTHORS π
the acpiprt driver was written by Mark Kettenis <kettenis@openbsd.org>. king behavior, we stan π«‘π
bestie, that's the whole page π this came out of the Debian build of the manual, dated July 16, 2013, filed under ACPIPRT(4) β and honestly? she ate. periodt. πβ¨π§
π¦ where this page comes from
- nixpkgs unstable: cvs-export
- Copyright (c) 2007 Michael Knudsen <mk@openbsd.org>
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms