Hi,
I am developing an embedded system using the i.MX8QX processor but I need support for the framebuffer inside Linux. I have a "working" /dev/fb0 device node but it is somehow locked to 16-bit colour.
Here is a snippet of kernel messages during bootup:
[ 3.134245] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 3.140910] [drm] No driver support for vblank timestamp query.
[ 3.146941] imx-drm display-subsystem: bound imx-drm-dpu-bliteng.2 (ops dpu_bliteng_ops)
[ 3.155274] imx-drm display-subsystem: bound imx-dpu-crtc.0 (ops dpu_crtc_ops)
[ 3.162718] imx-drm display-subsystem: bound imx-dpu-crtc.1 (ops dpu_crtc_ops)
[ 3.170815] imx-drm display-subsystem: bound bus@56220000:ldb@562210e0 (ops imx_ldb_ops)
[ 3.179496] [drm] Initialized imx-drm 1.0.0 20120507 for display-subsystem on minor 0
[ 3.288411] Console: switching to colour frame buffer device 160x50
[ 3.308826] imx-drm display-subsystem: fb0: imx-drmdrmfb frame buffer device
Using fbset to increase the bit-depth to 24 or 32 fails with an error:
# fbset -s
mode "1280x800"
geometry 1280 800 1280 800 16
timings 0 0 0 0 0 0 0
accel true
rgba 5/11,6/5,5/0,0/0
endmode
# fbset -depth 32
ioctl FBIOPUT_VSCREENINFO: Invalid argument
Any help would be greatly appreciated. The problem I have is that I must have access to the framebuffer at full 24/32 bit colour. The application I am porting to the new hardware runs on top of Qt 4.7 which doesn't have a working OpenGL driver (I've tested it) and at the present time the task of moving the code from Qt 4.7 to Qt 5.x is too great due to the amount of breaking changes between the two Qt versions and as a result I am stuck with Qt 4 for the present time.
Many thanks,
Andy