What is MADT?
Quick note explaining MADT for BIOS/UEFI and embedded firmware readers.
What is MADT?
MADT (Multiple APIC Description Table) describes interrupt-controller and processor interrupt information for the OS.
Why it matters
- Helps the OS understand platform devices or resources.
- Connects firmware description with OS driver behavior.
- Useful when debugging ACPI namespace, resource, or table issues.
Practical example
Example: if the OS does not bind a driver to an ACPI device, check _STA, _HID/_CID, and _CRS in that order.
Quick checklist
- Does the object/table appear in the ACPI namespace or OS table dump?
- Do _STA, _HID/_CID, and _CRS report consistent information?
- Do OS logs show ACPI errors or resource conflicts?
Quick takeaway
MADT is the contract between firmware description and OS interpretation.
Related notes
- ACPI Table Types: key points
- What is ACPI Namespace?
- What is AML?
- What is ACPI Method?
- What is XSDT?
Public references
Found this useful?
Save it or share it with someone learning firmware, BIOS/UEFI, and embedded systems.
Nội dung liên quan
Một số bài viết, ghi chú hoặc project có liên quan đến nội dung bạn vừa đọc.
What is DBG2?
Quick note explaining DBG2 for BIOS/UEFI and embedded firmware readers.
What is XSDT?
Quick note explaining XSDT for BIOS/UEFI and embedded firmware readers.
What is GPIO Operation Region?
Quick note explaining GPIO Operation Region for BIOS/UEFI and embedded firmware readers.
Biến note thành bài viết hoàn chỉnh
Notes là nơi ghi nhanh khái niệm.