[opensuse-arm] openGL ES vs openGL on aarch64 for Qt
Hi, Currently libqt5-qtbase is built with openGL ES target for aarch64, armv7 and armv6, whereas all others archs are built with openGL option. openGL ES is fine for armv6 and armv7, but I am thinking of switching aarch64 from openGL ES to openGL as aarch64 systems can now use standard PCIe gfx cards. Some aarch64 SoC still have embedded GPU which may support only ES version, though. Any opinion? Cheers, Guillaume IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi Guillaume, I'm okay with aligning aarch64 more with x86_64.. the timing is however funny because Qt just announced that over the long run they will stop embracing OpenGL.
openGL ES is fine for armv6 and armv7, but I am thinking of switching aarch64 from openGL ES to openGL as aarch64 systems can now use standard PCIe gfx cards. Some aarch64 SoC still have embedded GPU which may support only ES version, though.
Are you asking because of some compilation incompatibility somewhere ? I remember there were some apps (particularly in the KDE stack) blindly assuming that OpenGL would always be available in Qt.. I was hoping we could fix those over time. Also note that OpenGL support is on its (slow and very long) way out of Qt: https://www.qt.io/blog/qt-5.14-has-released The plan is to go with the more "native" lower level newer APIs like Vulkan, Metal etc. Or are you concerned about the lack of feature by feature compatibility with x86? that is a valid concern then I think, and if it makes any life easier we should align. :-) But the alignment could be by changing x86 to the more modern 3D apis .. although I don't know how painful that is going to be. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi Dirk,
-----Original Message----- From: Dirk Müller
Sent: 16 December 2019 11:45 To: Guillaume Gardet Cc: opensuse-arm@opensuse.org; Andreas Färber Subject: Re: openGL ES vs openGL on aarch64 for Qt Hi Guillaume,
I'm okay with aligning aarch64 more with x86_64.. the timing is however funny because Qt just announced that over the long run they will stop embracing OpenGL.
Thanks for the news.
openGL ES is fine for armv6 and armv7, but I am thinking of switching aarch64 from openGL ES to openGL as aarch64 systems can now use standard PCIe gfx cards. Some aarch64 SoC still have embedded GPU which may support only ES version, though.
Are you asking because of some compilation incompatibility somewhere ? I remember there were some apps (particularly in the KDE stack) blindly assuming that OpenGL would always be available in Qt.. I was hoping we could fix those
Yes, it is one of the reason, indeed.
over time. Also note that OpenGL support is on its (slow and very long) way out of Qt: https://www.qt.io/blog/qt-5.14-has-released The plan is to go with the more "native" lower level newer APIs like Vulkan, Metal etc.
Thanks for the link.
Or are you concerned about the lack of feature by feature compatibility with x86?
IMO, having less differences between architectures is generally better.
that is a valid concern then I think, and if it makes any life easier we should align. :-) But the alignment could be by changing x86 to the more modern 3D apis .. although I don't know how painful that is going to be.
We need to support this new API anyway, not sure if we could support both for some time. Fabian, you may have a clue? Cheers, Guillaume
Greetings, Dirk
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Moin, Am Montag, 16. Dezember 2019, 11:54:55 CET schrieb Guillaume Gardet:
Hi Dirk,
-----Original Message----- From: Dirk Müller
Sent: 16 December 2019 11:45 To: Guillaume Gardet Cc: opensuse-arm@opensuse.org; Andreas Färber Subject: Re: openGL ES vs openGL on aarch64 for Qt [...] over time. Also note that OpenGL support is on its (slow and very long) way out of Qt: https://www.qt.io/blog/qt-5.14-has-released The plan is to go with the more "native" lower level newer APIs like Vulkan, Metal etc.
The move is mostly to support multiple APIs instead of only OpenGL. There are more details here: https://www.qt.io/blog/qt-quick-on-vulkan-metal-direct3d
Thanks for the link.
Or are you concerned about the lack of feature by feature compatibility with x86?
IMO, having less differences between architectures is generally better.
that is a valid concern then I think, and if it makes any life easier we should align. :-) But the alignment could be by changing x86 to the more modern 3D apis .. although I don't know how painful that is going to be.
We need to support this new API anyway, not sure if we could support both for some time.
If you mean RHI, it has full OpenGL ES support.
Fabian, you may have a clue?
The option is to switch between OpenGL and OpenGL ES, it has no impact on Vulkan support. Many mobile GPUs have better/faster/higher OpenGL ES support than OpenGL, so I'm against switching. The RPi for instance does not do OpenGL well at all. Apart from fixing some build issues, are there other advantages? Cheers, Fabian
Cheers, Guillaume
Greetings, Dirk
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (3)
-
Dirk Müller
-
Fabian Vogt
-
Guillaume Gardet