I need some clarification on Framebuffer patching using WhateverGreen. I've read some of the guides and they all leave me with some questions due to not understanding some aspects of it.
With framebuffer patching, is it possible to add another framebuffer, or is that locked to the ig-platform-id you choose? And if so, is that where you have to use spoofing?
I'm also interested in the possibility of redirecting output to different physical ports, if adding a framebuffer to cover the ports I need isn't possible.
I have a ThinkPad T450 running Mojave, a Broadwell laptop with Intel HD5500, and a Lenovo UltraDock that has 2 sets of outputs on the back spread across 5 ports: A DP connector and an HDMI connector are tied together as one output, and another DP along with a DVI and VGA connector are together as another output. There's also a mini-DP port on the laptop itself.
My goal is to use 2 external monitors plugged into the dock, along with the laptop display itself. I can achieve this currently but only by using the mini-DP port on the laptop for one of the external displays, and one of ports on the dock for the other, because it views all of the connectors on the back as being tied to the same output. In Windows, it sets them up correctly as 2 outputs. So, I figure I need another framebuffer to cover all of the ports. But in lieu of that, if I could just disable the port on the laptop and instead enable a second output on the dock, that would work for me.
I read over the framebuffer patching guide using WhateverGreen, but it's not real clear on details such as redirection or adding framebuffers and such. I've used the debug version of WhateverGreen and dumped the native framebuffer information both to a file on the hard drive, and also did the one where you can view it in IORegistryExplorer, but I really don't know what to do with it in regards to seeing how the hardware is set in it and how to translate that over to the patching in the config.plist, especially when the output in both cases is entirely in hex. If I open the flat file version in Hackintool, it's not clear to me what it's even showing me or if anything changed in comparison to what it was already showing before I opened the file.
Another source of confusion is if the laptop internal display is con0 or con1... I notice the pre-built config.plist files offered by RehabMan and others never show a con0, but I read elsewhere that there is indeed a con0 assigned to an output... so is it always assigned to the internal display on a laptop, and just taken for granted that it's going to work, and thus usually no need to configure/show it in the framebuffer patching?
Any help would be greatly appreciated.
[link] [comments]
Post a Comment