mirror of
https://github.com/AskDavis/Getting-Started-With-ACPI.git
synced 2026-01-01 05:05:57 -08:00
Update Universal/apic.md
Co-authored-by: Dhinak G <dhinak2004@gmail.com>
This commit is contained in:
@@ -13,7 +13,7 @@ To get around this, we want to patch our APIC table to point the first CPU entry
|
||||
|
||||
## Dumping your DSDT and APIC tables
|
||||
|
||||
Dumping your DSDT and APIC table is quite easy, however some of the methods mentioned in [Getting a copy of our DSDT](../Manual/dumpmd) may not provide you will all the needed files. Methods that will provide a full dump:
|
||||
Dumping your DSDT and APIC table is quite easy, however some of the methods mentioned in [Getting a copy of our DSDT](../Manual/dump.md) may not provide you will all the needed files. Methods that will provide a full dump:
|
||||
|
||||
* acpidump.exe
|
||||
* Just run the program, don't give any specific arguments
|
||||
@@ -68,4 +68,4 @@ Processor (ProcessorName, ProcessorID, PBlockAddress, PblockLength)
|
||||
|
||||
Now if we look at the `ProcessorID` section, we notice it's `0x80`, but this doesn't match up with the first entry in our APIC table(`00`). Now we can get a clearer idea of what's wrong with out APIC table and why it kernel panics.
|
||||
|
||||
## Patching the APIC table
|
||||
## Patching the APIC table
|
||||
|
||||
Reference in New Issue
Block a user