- Joined
- Aug 13, 2011
- Messages
- 67
- Motherboard
- Lenovo Y700 - 15ISK (Clover)
- CPU
- i7-6700HQ / HM170
- Graphics
- HD530 / 1920x1080
- Mac
- Classic Mac
- Mobile Phone
It all depends on how they implement it. We need to wait for the first MBP with OPTIMUS ACPI table dumps to analyze them... and of course mountain lion's next DP. I hope to be an easy job but it's a bit of a long shot since apple uses a diff UEFI approach than most laptops... so its still not a guarantee.
Update:
Quoting what i said on another forum...
Update:
Quoting what i said on another forum...
Hey mackyreddy, unfortunately by deleting the geforce kext you removed the anchor for QE/CI. Also GF100Hal being loaded means no optimus is getting detected. GK100Hal.kext is what we must aim to.
Example: in my brief encounter with 10.7.4 for MBPs 2012 using my moddified DSDT with _PS0 method GK100Hal gets loaded, after analyzing it a bit i found that apple implemented th optimus driver in this kext. And if this is loading it means we are closer to achieving.
Atm im only launching suppositions because i dont have the time to test, anyway i assume that acer users with optimus can get it working on ML by simply editing their DSDT to inckude the optimus chunk of code. On our models its different... the channel from the gpu to the display is closed by default, it needs dsdt patching, and till we find what code does that it will take a while. Like i said i'm only assuming atm, i'll look into it in july to be sure. Either way, the full SSDT/DSDT and IOReg dump from the new optimus enabled MBP will help us. So if you get your hand on them, please do share!
Edit: GK100Hal and GF100Hal are connected to nvdaresman.kext, removing resman forbids the other kexts to load. This wasn't the case before, another worrying thing is that the system is asking for MUXControl when GK100Hal is loaded....