Thanks for the info.
I’ve tried forcing one of the preset edid blobs to see the process but the /lib/firmware directory is read only in user space, how can this be overcome?
The display used is a hobbyist one and can be found here.
Something interesting I found is that the resolution is not actually bad when connected to the module. In fact it is better than in the TEI. This was not visible before because of the jittering, but when zoomed in the jittering goes away. I recorded a video showing this. It can be found here.
Another thing is that when executing get-edid | edid-decode on the module the output is slightly different from the laptop, and shows that the EDID read is compliant.
The output of the commands is:
EDID version: 1.3
Manufacturer: ADA Model 2100 Serial Number 20000080
Made in week 28 of 2009
Digital display
Maximum image size: 47 cm x 26 cm
Gamma: 1.00
DPMS levels: Off
RGB color display
First detailed timing is preferred timing
Display x,y Chromaticity:
Red: 0.6484, 0.3388
Green: 0.2822, 0.6025
Blue: 0.1425, 0.0703
White: 0.3134, 0.3291
Established timings supported:
Standard timings supported:
Detailed mode: Clock 50.250 MHz, 476 mm x 268 mm
1024 1068 1156 1344 hborder 0
600 603 609 625 vborder 0
-hsync -vsync
VertFreq: 59 Hz, HorFreq: 37388 Hz
Serial number: 0
Monitor ranges (GTF): 56-75Hz V, 30-83kHz H, max dotclock 210MHz
Monitor name: HDMI
Checksum: 0x89 (valid)
So the problem is the timings and not the resolution. As the resolution is non standard and is processed correctly, it is implied that the EDID is correct, which is backed up by the decoder. The jitter could be a re-drawing problem, but this does not make sense as when left untouched on a still image showing the whole screen it never settles like it does when zoomed in.
Kind regards,
Klitos