But if I enable HiDPI : there's a dramatic performance drop and high GPU usage. I was not aware that most userspace methods are now shims for remotely calling the embedded code. I have a macbook pro 13 2018(Iris Plus 655, quad-core) with a 2K external monitor. I guess I'll have to look into how the analysed exploit is using the RPC, and also check the methods assembly from inside the firmware blob itself. The Thunderbolt ports however send the DDC command as expected when IOAVServiceWriteI2C is calledĪfter from Asahi Linux pointed out the DCPAVFamilyProxy kexts, I've looked into it and I found some different writei2c methods and some MCDP29xx specific code, but no clue on how to call them from userspace. When sending DDC commands through the IOAVServiceWriteI2C call, monitors connected to the HDMI port lose video signal, or flicker or completely crash and need a power cycle to get them back. (that is also the reason why even the newest MacBook and Mac Studio have only HDMI 2.0, that's the most the converter chip supports ) It's not clear what's going on, but it seems that the HDMI port of the 2018+ Macs uses an MCDP29xx chip inside, which converts the HDMI signal to DisplayPort internally, so that Apple doesn't have to decode both HDMI and DP video signals. Users have to either switch to a Thunderbolt port to get native brightness control for their monitor, or use a software dimming solution like Gamma Table alteration. The DCP is actually the thing that's stopping me from providing native brightness control on the HDMI port of the newer Macs inside Lunar ( ). I wish I had the expertise to do such in-depth reverse engineering of firmware blobs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |