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

Rewrite of ACPI section

Browse Source
This commit is contained in:
khronokernel
2020-02-06 22:17:35 -07:00
parent c6f1f992b1
commit 41e9791099
3 changed files with 44 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

35
Desktops/desktop-ec.md
View File

@@ -10,7 +10,7 @@ To find out what EC you have, open your decompiled DSDT and search for `PNP0C09`
As you can see our `PNP0C09` is found within the `Device (EC0)` meaning this is the device we want to hide from macOS(others may find `H_EC`, `ECDV`, etc, everyone's systems will be different). Now grab our SSDT-EC and uncomment the EC0 function(remove the `/*` and `*/` around it):
* [SSDT-EC-USBX](https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/AcpiSamples/SSDT-EC-USBX.dsl)
* For Skylake+ and all AMD systems
* For Skylake and newer and all AMD systems
* [SSDT-EC](https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/AcpiSamples/SSDT-EC.dsl)
* For Broadwell and older
@@ -35,36 +35,42 @@ External (_SB_.PCI0.LPCB.EC0, DeviceObj)
*/ <- REMOVE THIS
```
But looking back at the screenshot above we notice something, our ACPI path is different: `PC00.LPC0` vs `PCI0.LPCB`. This is very important especially when you're dealing with Intel consumer vs Intel HEDT and AMD, `PC00.LPC0` is common on Intel HEDT while `PCI0.SBRG` is common on AMD. And they even come with name variation such as `EC0`, `H_EC`, `PGEC` and `ECDV`, so there can't be a one size fits all SSDT, **always verify your path and device. DO NOT ASSUME**.
But looking back at the screenshot above we notice something, our ACPI path is different: `PC00.LPC0` vs `PCI0.LPCB`. This is very important especially when you're dealing with Intel consumer vs Intel HEDT vs AMD, `PC00.LPC0` is common on Intel HEDT while `PCI0.SBRG` is common on AMD. And they even come with name variation such as `EC0`, `H_EC`, `PGEC` and `ECDV`, so there can't be a one size fits all SSDT, **always verify your path and device. DO NOT ASSUME**.
* Finding the LowPinCount path:
* Intel: Search `Name (_ADR, 0x001F0000)`
* AMD: Search `Name (_ADR, 0x00140003)`
* Finding the PCI path:
* Search for `PNP0A08` (If multiple show up, use the first one)
* Intel: Search `PNP0A08` (If multiple show up, use the first one)
* AMD: Assume `PCI0`(most AMD DSDTs don't declare the PCI path directly)
And make sure to scroll to the bottom as the new Fake EC function also need the correct path to replace the old EC. **Do not rename the EC device itself**, this is our fake EC we're using for macOS to play with so leave Leave `Device (EC)` alone. **Just change the path!**
And make sure to scroll to the bottom as the new Fake EC function also need the correct path to replace the old EC. **Do not rename `Device (EC)`**, this is our fake EC we're using for macOS to play with so leave `Device (EC)` alone. **Just change the path!**
> What happens if multiple `PNP0C09` show up
When this happens you need to figure out which is the main and which is not, it's fairly easy to figure out. Check each controller for the following properties:
* `_HID`
* `_CRS`
* `_GPE`
* `_HID` (Hardware ID)
* `_CRS` (Current Resource Settings)
* `_GPE` (General Purpose Events)
> What happens if no `PNP0C09` show up?
This means your SSDT can be *almost* complied, the main thing to watch for is whether your DSDT uses `PCI0.LPCB` or not. The reason being is that we have a FakeEC at the bottom of our SSDT that needs to connect properly into our DSDT. Gernally AMD uses `SBRG` while Intel HEDT use `LPC0`, **verify which show up in your DSDT**.
So what this means: EC faking is not mandatory for booting, instead only **recommended for proper USB power**.
You can check by just searching for `Name (_ADR, 0x001F0000)`(this only works for Intel, AMD's controller is found at `Name (_ADR, 0x00140003)`). This address is used for Low Pin Count devices(LPC) but the device name can vary between `LPCB`, `LBC` or `LBC0`.**Again, double check your device. DO NOT ASSUME**:
So how do I make an SSDT without an EC? Well we'll only create a Fake EC for macOS to play with, this allows for AppleBusPowerController to load and handle our USB properly. To make the actual SSDT, its *almost* plug and play as no uncommenting needed. The main thing that needs to be changed:
* LowPinCount path
* PCI path
We want to make sure the SSDT hooks into our DSDT correctly so we need to make sure the ACPI path is correct:
* Finding the LowPinCount path:
* Intel: Search `Name (_ADR, 0x001F0000)`
* AMD: Search `Name (_ADR, 0x00140003)`(Almost always will be called `SBRG`)
* AMD: Search `Name (_ADR, 0x00140003)`
* Finding the PCI path:
* Search for `PNP0A08` (If multiple show up, use the first one)
* Intel: Search `PNP0A08` (If multiple show up, use the first one)
* AMD: Assume `PCI0`(most AMD DSDTs don't declare the PCI path directly)
![](https://cdn.discordapp.com/attachments/456913818467958789/670148514197667840/Screen_Shot_2020-01-23_at_11.08.30_PM.png)
@@ -73,7 +79,7 @@ You can check by just searching for `Name (_ADR, 0x001F0000)`(this only works fo
Once you find out, change `PCI0.LPCB` to your correct path:
```text
Scope (\_SB.PCI0.LPCB)
Scope (\_SB.PC00.LPC0)
{
Device (EC)
{
@@ -93,9 +99,8 @@ Scope (\_SB.PCI0.LPCB)
}
```
## Correcting USB Power
> Hey what about USBX? Do I need to do anything?
USBX is universal across all systems, it just creates a USBX device that forces USB power properties. This is crucial for fixing Mics, DACs, Webcams, Bluetooth Dongles and other high power draw devices. This is not mandatory to boot but should be added in post-install if not before. Note that USBX is only used on skylake+ systems, Broadwell and older can ignore and that USBX requires a patched EC to function correctly
For those who want a deeper dive into the EC issue: [What's new in macOS Catalina](https://www.reddit.com/r/hackintosh/comments/den28t/whats_new_in_macos_catalina/)