Skip to content

Remove unnecesssary gl4es configs#29

Open
vasucp1207 wants to merge 1 commit into
vicharak-in:mainfrom
vasucp1207:main
Open

Remove unnecesssary gl4es configs#29
vasucp1207 wants to merge 1 commit into
vicharak-in:mainfrom
vasucp1207:main

Conversation

@vasucp1207

Copy link
Copy Markdown
Member

There is no need for GL4ES, since Mesa3D already supports up to OpenGL 3.1. This GL4ES solution does not even work properly.

@avi951 avi951 requested a review from djkabutar July 30, 2025 06:26

@djkabutar djkabutar left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The gl4es is working for both vaaman and axon, on vaaman we are still using mali gpu drivers and we do not have support for opengl in that, we just have support for open gl es.

In axon, we are providing jammy image in that as well we are using mali drivers only, the same case applies here as well.

Only in the newer noble image of axon we are using panfrost drivers which supports opengl 3.1 natively!

So we need to put a check here for the menu, if we are using mali drivers then this menu should be appearing otherwise not.

Last but not least, check the previous commit messages for little help in the message, we do not follow this approach for the commit message.

@vasucp1207

vasucp1207 commented Jul 30, 2025

Copy link
Copy Markdown
Member Author

See this link both T864(vaaman, its a variant of T860) and G610(axon) gpu supports upto gl3.1 while gl4es translation does not work for 3.x versions. Also there is no proper shader translation in gl4es.

@djkabutar

Copy link
Copy Markdown
Member

Yes, you are right about that but in jammy version of images for vaaman and axon there is no panfrost support in the kernel, so opengl 3.1 won't work there, we need to give opengl support in those images as well. For that we need to put a check for this menu.

@vasucp1207

Copy link
Copy Markdown
Member Author

Ok, got it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants