Anonymous user
DSDT: Difference between revisions
→Purpose of DSDT
| [unchecked revision] | [unchecked revision] |
(→ACPI) |
|||
Line 44:
Most likely you will never generate such a binary. But it helps if you know it's source form when you came to decode.
===Purpose of DSDT===
When your OS boots, it should parse the memory for [[ACPI]] tables. Then locate DSDT (and other tables as well, like [[FADT]]), and decode it to get the list of installed devices. If you have that list, it's rather easy to load [[Device_Driver_Interfaces|device driver]] for each.
Also note that there are buggy tables, so you should always kept the possibility to load DSDT data from a user provided file instead. This file could be located in your [[initrd|initial ramdisk]], loaded with your kernel along on boot. That would solve the chicken-egg problem of loading the DSDT file from a device that's IO addresses is defined in the DSDT.
| |||