DSDT: Difference between revisions
Jump to navigation
Jump to search
| [unchecked revision] | [unchecked revision] |
Content deleted Content added
m Added that table has header and a reference for validation. |
m Undo revision 23674 by Legiodetenebris (talk) |
||
| Line 4: | Line 4: | ||
===Introduction=== |
===Introduction=== |
||
{{stub}} |
{{stub}} |
||
DSDT stands for ''Differentiated System Description Table''. It Is a major [[ACPI]] table and is used to describe what peripherals the machine has. Also holds information on PCI IRQ mappings and power management. For example when powering down by the OS, it should find the _S5 object which describes how to do that. It is pointed to by the [[FADT]] |
DSDT stands for ''Differentiated System Description Table''. It Is a major [[ACPI]] table and is used to describe what peripherals the machine has. Also holds information on PCI IRQ mappings and power management. For example when powering down by the OS, it should find the _S5 object which describes how to do that. It is pointed to by the [[FADT]] |
||
<br /> |
|||
<br /> |
|||
As every ACPI table, it has header section and '''should''' be validated ([https://wiki.osdev.org/RSDT#Validating_the_RSDT ACPI table validation]). |
|||
===How hardware manufacturers generate it=== |
===How hardware manufacturers generate it=== |
||
You can use an ASL (ACPI Source Language) compiler to generate DSDT AML (ACPI Machine Language) bytecode from a C-like language. To get an idea, take a glimpse on Bochs source: |
You can use an ASL (ACPI Source Language) compiler to generate DSDT AML (ACPI Machine Language) bytecode from a C-like language. To get an idea, take a glimpse on Bochs source: |
||