- Joined
- Jul 21, 2011
- Messages
- 379
- Motherboard
- Zbook G5 17"
- CPU
- i7
- Graphics
- AMD WX-4170
- Mac
Edit- I see what you mean now following IPCW...
Maybe disabling PRRE or removing (zeroing) the Memory overlap is a better (less risky) solution.
What I could find is that in a MacBookPro PMST is almost identical to my PWRM except for a couple of fields related to changing the IGPU power states _PS0 and _PS3.
This is also above my pay grade, but I would venture to say they are more than related,and as long as we don't rename PWRM to PMST, then OSX won't really even use the memory. My guess is that OSX likes the range to be there and available, (for PMST) but since we don't have that, then it's just sitting there.
As to what we would gain/loose if we used it... who knows, probably hybernation related.
MacBookPro 16,1
ZBook G5
Maybe disabling PRRE or removing (zeroing) the Memory overlap is a better (less risky) solution.
What I could find is that in a MacBookPro PMST is almost identical to my PWRM except for a couple of fields related to changing the IGPU power states _PS0 and _PS3.
This is also above my pay grade, but I would venture to say they are more than related,
As to what we would gain/loose if we used it... who knows, probably hybernation related.
MacBookPro 16,1
ZBook G5
Last edited: