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

Misc Fixes

Browse Source 
- Inital lint'ing
- Clean up README.md table
- Add CONTRIBUTING.md
- Add TROUBLESHOOTING.md
This commit is contained in:
Mykola Grymalyuk
2020-04-18 13:29:12 -06:00
parent fb33ef4979
commit 17f7c8aba3
43 changed files with 13509 additions and 164 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
Universal/plug.md
View File

@@ -2,7 +2,7 @@
CPU naming is fairly easy to figure out as well, open your decompiled DSDT and search for `Processor`. This should give you a result like this:
![](https://i.imgur.com/U3xffjU.png)
![](/images/Universal/plug-md/processor.png)
As we can see, the first processor in our list is `PR00`. This is what we'll be applying the `plugin-type=1` property too. Now grab [SSDT-PLUG](https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/AcpiSamples/SSDT-PLUG.dsl) and replace the default `CPU0` with our `PR00`. There's a couple things to note:
@@ -13,11 +13,11 @@ So in our final example, we'd have `_SB_.PR00` and `\_SB.PR00`
There are also some edge cases with `Processor`, specifically on HEDT series like X79, X99 and X299. This edge case is that the ACPI path is much longer and not so obvious:
![](https://i.imgur.com/HzOmbx2.png)
![](/images/Universal/plug-md/processor-2.png)
If we then search for instances of `CP00` we find that it's ACPI path is `SB.SCK0.CP00`:
![](https://i.imgur.com/CtL6Csn.png)
![](/images/Universal/plug-md/cp00.png)
So for this X299 board, we'd change `\_PR.CPU0` with `\_SB.SCK0.CP00` and `External (_PR_.CPU0, ProcessorObj)` with `External (_SB_.SCK0.CP00, ProcessorObj)`