Using 5.02 sdk; compiled QT with SGX libs. Also have an LCD driven on Vout[0] (dvo2). QT with powervr works fine when using HDMI port. QT works fine on redirected graphics0 to dvo2. The problem: QT with powervr on dvo2 with modified timing has garbled graphics.
In another post, I showed I got the LCD to work with the following redirections:
echo 0 > /sys/devices/platform/vpss/graphics0/enabled
echo 1 > /sys/devices/platform/vpss/display1/enabled
echo 1:dvo2 > /sys/devices/platform/vpss/graphics0/nodes
echo 0 > /sys/devices/platform/vpss/display1/enabled
echo 75010,1366/50/67/30,768/7/17/5,1 > /sys/devices/platform/vpss/display1/timings
fbset -xres 1366 -yres 768 -vxres 1366 -vyres 768
fbset -depth 32 -rgba 8/16,8/8,8/0,0/0
echo 1 > /sys/devices/platform/vpss/display1/enabled
This will work for QT without accelerated video, but not with it enabled; I think the powervr isn't working off the same screen resolution settings.
The opengl QT hello example is interesting; the overall window is drawn correctly, but the spinning 3d QT symbol area is garbled. It looks like it is drawn expecting different screen dimensions from that of the main window. All full screen accelerated examples are garbled as well.
Are there additional settings I should be implementing when I run LCD/custom timing on VOUT[0]?
Thanks!
-Dal
