Revision as of 20:43, 7 March 2012 (view source) osdev>Turdus (→‎Purpose of DSDT) ← Older edit		Revision as of 17:23, 13 October 2014 (view source) osdev>Sapphirebeauty mNo edit summary Newer edit →
Line 46: When your OS boots, it should parse the memory for [[ACPI]] tables. Then locate DSDT (and other tables as well, like [[SSDT]]), 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~~keep 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 isare defined in the DSDT. ==See Also==

DSDT: Difference between revisions

DSDT (view source)