Hi @leon.tx
I’ve just seen your commit here on next branch of weston container for imx8 platform.
In the commit comment I read:
This is a new switch from Weston 10 (which previously seems to have
been enabled all the time).
This flag tells Weston to load the g2d renderer libraries that come
from libg2d-viv.
Related-to: TCCP-768
I’m curious;
if I’m right, Torizon OS 6.7 (and 6.8 too) comes with weston 10.0.1
Did you add that command line switch because you saw some graphic performance penalization without it?
If this is the case, is this change included in the container torizon/weston-imx8:next available on dockerhub?
Can I use it with Torizon OS 6.7 (6.8) instead of torizon/weston-vivante:3.4?
Hi, I’m the Toradex AI Assistant. I’m in early beta, and I would appreciate your feedback.
The Toradex Support team will follow up with you shortly!
Did you like my answer?
I don’t have specific information about the commit mentioned or the exact details of the changes made by @leon.tx. However, I can provide some general insights based on the context provided.
General Insights on Weston and G2D Renderer
Weston 10 and G2D Renderer:
Weston 10 introduced a new switch to load the G2D renderer libraries from libg2d-viv.
The G2D renderer can potentially improve graphical performance by offloading certain rendering tasks to the GPU.
Torizon OS Versions:
Torizon OS 6.7 and 6.8 come with Weston 10.0.1, which supports this new switch.
Performance Considerations:
If the switch was added, it might be due to observed performance improvements when using the G2D renderer.
Without the switch, there could be a performance penalty as the rendering tasks might not be optimally offloaded to the GPU.
Container Availability:
The change should be included in the torizon/weston-imx8:next container available on Docker Hub.
You can use this container with Torizon OS 6.7 or 6.8 instead of torizon/weston-vivante:3.4.
Recommendations
Testing: Before fully switching to the new container, it is advisable to test it in your environment to ensure it meets your performance and stability requirements.
Documentation: Check the official Toradex documentation or release notes for any specific instructions or additional details regarding the use of the G2D renderer with Weston 10.
If you need more specific information or confirmation about the commit and its implications, I recommend reaching out directly to the Toradex support team or @leon.tx for detailed insights.
if I’m right, Torizon OS 6.7 (and 6.8 too) comes with weston 10.0.1
Correct.
Did you add that command line switch because you saw some graphic performance penalization without it?
No, this was added because of a change from the weston-imx fork itself from version 10 to 12. Previously it just loaded the necessary renderer libraries directly but now you have to force it with the --use-g2d flag.
If this is the case, is this change included in the container torizon/weston-imx8:next available on dockerhub?
Correct, all images tagged next are built from the tip of the next branch. It takes around 2~3mins after a commit lands for the images to be overwritten to DockerHub.
Can I use it with Torizon OS 6.7 (6.8) instead of torizon/weston-vivante:3.4?
Very much not recommended. next is meant to be used with Torizon OS 7, based on Scarthgap. Technically, these images are meant to be specifically used with the integration manifest. Even if you tried there are probably a lot of inconsistencies between the userland/kernel drivers because downstream kernels do break userspace from release to release.
You can, however, try to use Torizon OS 7 and next images already. Quite a few things (like Weston, gputop, some basic integration with GL libraries) are already working. You’ll have to pick out the exact commands from the tests folder torizon-containers/tests/suites/imx8 at next · torizon/torizon-containers · GitHub, which are steadily being added/updated and you may find a lot of issues, but we welcome feedback either way, specially now that we can break a major and possibly make life easier for the users.
you mean “a new switch that was not present in weston 10”.
Oops, yea, now that I’m reading it back I can see how that would make one confused. I’ll overwrite that message to make it clearer (which is okay because it’s a development branch ).
Nightlies are available from the integration feed with Easy Installer and from Torizon Cloud. Although we don’t yet have an official recommendation on updating from 6 to 7 directly from Torizon Cloud, as of today, it’s mostly working with all boards (mainly due to the previous bootloader being able to boot both versions). But again, we don’t know if things will stay this way.
).