Hi Suzuki-san Thank you for your advice. I will check and discuss with my team members. Thanks a lot.
J Best Regards Zhou Mingying From: Tasuku Suzuki <Tasuku.Suzuki@xxxxxx>
Hi Mingying, As you figured it out, Qt only supports ivi-application and ivi-controller now. I recommend you to write what you need in/for the Qt project. Like AGL, Qt uses JIRA and Gerrit. So it will be easy to push your patch to the upstream project. See these pages for details. I wish I could help you
😉 Best Regards, -- Tasuku Suzuki tQCS K.K. - the Qt Consulting Solution M. +81 70 4001 0910 | Skype. Tasuku.Suzuki 差出人:
Zhou, Mingying <zhoumy@xxxxxxxxxxxxxx> Hi Suzuki-san I’m very sorry that I have another question. Does Qt Compositor support ivi-wm protocol? Or how can I make Qt Compositor support ivi-wm protocol?
My Goal is to use Qt Wayland Compositor to instead of Weston. When I kill Weston, start qt compositor(example: minimal-qml),
Then I try to start agl-windowmanager , the error message
“ivi_wm is not available” is output. the detail error message is as bellow -------------------- May 8 17:32:28 m3ulcb daemon.info
afbd-windowmanager-service@0.1[4276]: ivi_wm not available
May 8 17:32:28 m3ulcb daemon.info
afbd-windowmanager-service@0.1[4276]: [Warning] The ilm_control_context is already destroyed
May 8 17:32:28 m3ulcb daemon.info
afbd-windowmanager-service@0.1[4276]: [3081716.595] [wm ERROR] [wm_layer_control.cpp, init(), Line:88] >>> Wait to start weston ...
-------------------- It seems that agl-windowmanager
–service needs wayland-ivi-extension’s ivi_wm protocol. Weston support ivi-wm, so agl-windowmanager-service can work with Weston well,
and QtCompositor does not support ivi-wm, so agl-windowmanager-service can’t
work. Then I compared the protocols supported by QtCompositor and Weston, The Weston just supports ivi-application and ivi-hmi-controller. And QtCompositor supports ivi-application and ivi-controller. Maybe I should make QtCompositor use ivi-controller protocol. ( the ivi-controller is supported by QtCompositor, but it seems no one use it) Can you give me some advices? Thanks. ----------------------------------------- Wayland-ivi-extension supports the bellow protocols: ivi-application.xml ivi-input.xml ivi-share.xml ivi-wm.xml QtCompositor supports the bellow protocols: ivi-application.xml ivi-controller.xml https://doc.qt.io/qt-5.9/qtwaylandcompositor-attribution-wayland-ivi-extension-protocol.html Weston supports the bellow protocols: ivi-application.xml ivi-hmi-controller.xml ----------------------------------------- Best Regards Zhou Mingying From:
automotive-discussions-bounces@xxxxxxxxxxxxxxxxxxxxxxxxx <automotive-discussions-bounces@xxxxxxxxxxxxxxxxxxxxxxxxx>
On Behalf Of Zhou, Mingying Hi Suzuki-san Thank you very much When I add kms and gbm, it seems that the program can work. Thanks. Best regards Zhou Mingying From: Tasuku Suzuki <Tasuku.Suzuki@xxxxxx>
Hi, Can you check config.summary file which is generated during configure in qtbase? When gbm is available and enabled, a plugin called libqeglfs-kms-integration.so will be built. I recommend you to start simpler Qt apps such as qmlscene first with -platform eglfs. If it works, any QtWaylandCompositor apps should work with eglfs as a wayland
compositor. Best Regards, -- Tasuku Suzuki tQCS K.K. - the Qt Consulting Solution M. +81 70 4001 0910 | Skype. Tasuku.Suzuki 差出人:
automotive-discussions-bounces@xxxxxxxxxxxxxxxxxxxxxxxxx <automotive-discussions-bounces@xxxxxxxxxxxxxxxxxxxxxxxxx>
が Zhou, Mingying <zhoumy@xxxxxxxxxxxxxx>
の代理で送信 Hi |
_______________________________________________ automotive-discussions mailing list automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions