fb2 with eglfs
I manage to show graphic on fb2 by outputing image to /dev/fb0 (using psplash utility)
Now I try to do the same with eglfs application qt 5.5.
It already works with fb0.
But on trying to do the same with fb2, it shows nothing on the display, even though there are no errors:
root@dm814x:~/Naval# export QT_QPA_EGLFS_FB=/dev/fb2 root@dm814x:~/Naval# ./Main -platform eglfs QT_QPA_EGLFS_FB=/dev/fb2 QIconvCodec::convertFromUnicode: using Latin-1 for conversion, iconv_open failed QML debugging is enabled. Only use this in a safe environment. QIconvCodec::convertToUnicode: using Latin-1 for conversion, iconv_open failed Unable to query physical screen size, defaulting to 100 dpi. To override, set QT_QPA_EGLFS_PHYSICAL_WIDTH and QT_QPA_EGLFS_PHYSICAL_HEIGHT (in millimeters). ezBuilder::BuildEnvironment  Success qrc:/qml/Resources/qml/UiMainWindow.qml:127: TypeError: Cannot read property 'szActiveAlert' of undefined .............ezBuilder::BuildInitializeSystem [...........] Success QObject: Cannot create children for a parent that is in a different thread. (Parent is UiMsgRtToGuiHandler(0x7bd1d8), parent's thread is QThread(0xa9db30), current thread is QThread(0xae8d8) QObject: Cannot create children for a parent that is in a different thread. (Parent is UiMsgAppToGuiHandler(0x7bc9a0), parent's thread is QThread(0xa9ded0), current thread is QThread(0xae8d8) ezBuilder::BuildRunSystem [...........] Success PeriodicMonitorDataCollection() COMM RESUME SetEnableDisableAllExportedDB(): SetEnableDisable(1) m_nNumberOfExportedCouples MonitoringManager::HandleMonitorCommunicationResume [DE connected!]
Is there any idea what's the problem ?
I know nothing about fb2, whatever that is, but here's an idea:
You write that there are no errors, but your listing is full of errors! Try to locate them in the debugger and fix them. That's the general idea...
One error complains about threads; you should be able to figure out in which thread things run and perhaps change the architecture.
I chcked the errors. The same errors also appear when using /dev/fb0.
I think the problem is elsewhere in this case.