volram

There is a big problem well known for the ATI mobility users: 1600x900 screen in LVDS is very difficult to attain. I think I have found the real motive for this. ATI uses, in some cases,  the eDP output for connect with the internal lcd probably because of the high resolution of the panel. In my case the output is the following:


Connector Object Id [14] which is [LVDS]
encoder obj id [0x21] which is [INTERNAL_UNIPHY2 (osx txmit 0x12 [duallink 0x2] enc 0x4)] linkb: false
Connector Object Id [5] which is [VGA]
encoder obj id [0x15] which is [INTERNAL_KLDSCP_DAC1 (osx txmit 0x00 enc 0x10?)] linkb: false
Connector Object Id [12] which is [HDMI_TYPE_A]
encoder obj id [0x1e] which is [INTERNAL_UNIPHY (osx txmit 0x20 [duallink 0x0] enc 0x1)] linkb: true

But the transmitter 12/04 or 12/01 give me a black screen or half resolution (even with the dual link patch that can be made with chameleon, DSDT or via ATY_init plist).
The root of the problem, then, I think is the connector type. Reading the Linux driver info ( http://cgit.freedesk...ecac298b8d441d0) in the section Connector Object ID Definition has it:
-#define CONNECTOR_OBJECT_ID_eDP    0x14
As you can see, the connector that is identified as LVDS with the redsox bios decoder is really the eDP decoder. Kizwan has noted that some Imacs uses that port: http://www.insanelym...0#entry1662530.
The problem is that with the Shrike framebuffer Mountain Lion simply not load the GUI in my HP. How to solve that? I mean how to patch a framebuffer with this info i.e eDP output to enable LVDS connected via eDP. What are the connector type and control flags?