- Joined
- Sep 22, 2011
- Messages
- 1,520
- Motherboard
- HP EliteDesk 800 G5 Mini
- CPU
- i9-9900
- Graphics
- UHD 630
- Mac
- Mobile Phone
@theroadw My only concern with my originally proposed PRRE._STA=0 is that something in hardware is using PRRE's reserved memory regions and that a change in ACPI won't prevent the conflict. I am becoming more and more convinced that the safest way to handle the conflict you observed is to change Device PMCR (something we do control).
EDIT: I need to remind myself that we are running macOS on Windows hardware. Duplicating ACPI from a real Mac may not always be the best solution (although I do start with that approach in my hacks).
Name (_CRS, ResourceTemplate () // _CRS: Current Resource Settings
{
Memory32Fixed (ReadWrite,
0xFE020000, // Address Base
0x00010000, // Address Length
)
})
@theroadw As long as we're guessing about how these reserved memory buffers work, I mapped out the Memory32Fixed buffers declared within the HP EliteDesk 800 G4 Mini DSDT. There are "free" regions that are unclaimed: 0xFE020000-0xFE100000, 0xFED94000-0xFEE00000 and 0xFEF00000-0xFF000000. If we believe that Device PMCR just needs a free buffer of length 0x00010000, then for the HP EliteDesk 800 G4, the following PMCR._CRS might be acceptable:
Code:Name (_CRS, ResourceTemplate () // _CRS: Current Resource Settings { Memory32Fixed (ReadWrite, 0xFE020000, // Address Base 0x00010000, // Address Length ) })
EDIT: I am currently running with with this PMCR:
View attachment 516427
OperationRegion (PMST, SystemMemory, 0xFE000000, 0x1EFF)
Field (PMST, DWordAcc, NoLock, Preserve)
{
CMDR, 32,
IBSY, 1,
IERR, 1,
...
OperationRegion (PWMR, SystemMemory, PWRM, 0x1E30)
Field (PWMR, DWordAcc, NoLock, Preserve)
{
CMDR, 32,
IBSY, 1,
IERR, 1,
...