[ASK] what did clover ATI Framebuffer data patch actually do? and why some of the framebuffer doesn't exist in the binary file?

[pink101]

So, here's what i think clover do when it patch ati framebuffer, first it read a cached kext, then it search the original hex value of the connector, then it changed the value with the new one. Is it correct? now, here's what i find confusing... let's say that i want to patch AMD7000Controller.kext, in that kext, i want to patch "AJI" framebuffer with a new value, so clover try to find the hex value of "AJI" connector then replace it with the new one, simple right? but when i search the AMD7000Controller binary file for other framebuffer, some of them didn't exist in the binary, for example, i tried to patch "Ramen" framebuffer, from various source, it said that:

Ramen (6) @ 0xeba70
LVDS, HDMI, DP, DP, DP, DP
020000000001000039050108000000002001050600000000
000800000402000000010200000000001000030500000000
000400000403000000010343000000001102010100000000
000400000001000000010431000000002103040300000000
000400000403000000010563000000001204020200000000
000400000001000000010651000000002205040300000000

So i open a hex editor and search for:

020000000001000039050108000000002001050600000000000800000402000000010200000000001000030500000000000400000403000000010343000000001102010100000000000400000001000000010431000000002103040300000000000400000403000000010563000000001204020200000000000400000001000000010651000000002205040300000000

but, it turns out that hex editor couldnt find that hex value in AMD7000Controller,

 

most of the framebuffer exist in the AMD7000Controller, but some doesnt, If this is the case, then, where does clover find the original framebuffer to be patched? am i missing something?

 

 

Edited July 31, 2020 by pink101