AskDavis/Getting-Started-With-ACPI
1
0
Fork 0
mirror of https://github.com/AskDavis/Getting-Started-With-ACPI.git synced 2026-01-01 05:05:57 -08:00
Code Issues Packages Projects Releases Wiki Activity

Switch to submodule

Browse Source
This commit is contained in:
Dhinak G
2020-12-29 13:30:21 -05:00
parent c0f0e1089e
commit ba5e41e388
32 changed files with 112 additions and 135 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
Universal/plug-methods/manual.md
View File

@@ -16,7 +16,7 @@ To find the ACPI pathing, you have 2 methods:
### DSDT
CPU naming is fairly easy to figure out, first open your decompiled DSDT you got from [Dumping the DSDT](/Manual/dump.md) and [Decompiling and Compiling](/Manual/compile.md) with either maciASL(if in macOS) or any other text editor if in Windows or Linux(VSCode has an [ACPI extension](https://marketplace.visualstudio.com/items?itemName=Thog.vscode-asl) that can also help).
CPU naming is fairly easy to figure out, first open your decompiled DSDT you got from [Dumping the DSDT](/Manual/dump.md) and [Decompiling and Compiling](/Manual/compile.md) with either MaciASL(if in macOS) or any other text editor if in Windows or Linux(VSCode has an [ACPI extension](https://marketplace.visualstudio.com/items?itemName=Thog.vscode-asl) that can also help).
Next search for `Processor`. This should give you a result like this:
@@ -26,7 +26,7 @@ As we can see, the first processor in our list is `SB.PR00`. This is what we'll
**X99 and X299 note**:
Due to the different DSDT structure of these systems, you'll need to to actually check in multiple places as the pathing isn't as obvious:
Due to the different DSDT structure of these systems, you'll need to actually check in multiple places as the pathing isn't as obvious:
![](../../images/Universal/plug-md/processor-2.png)