Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Force use of particular api #248

Closed
2e0byo opened this issue Feb 20, 2023 · 3 comments
Closed

Force use of particular api #248

2e0byo opened this issue Feb 20, 2023 · 3 comments

Comments

@2e0byo
Copy link

2e0byo commented Feb 20, 2023

Is it possible to force surfman to use a particular api? On my system (horrible nvidia card, sorry) GlEs works, but Gl doesn't. Glutin returns a GlEs context, whereas surfman hands out a Gl, which subsequently fails (probably due to nonsense in the driver).

@jdm
Copy link
Member

jdm commented Feb 20, 2023

What surfman APIs are you using? What platform are you on?

@jdm
Copy link
Member

jdm commented Feb 20, 2023

For what it's worth, surfman currently only makes use of GLES with ANGLE and Android.

@2e0byo
Copy link
Author

2e0byo commented Feb 20, 2023

I'm actually hacking emacs-ng, which uses webrender_surfman (by default) to set up the GL context. Ergo there's abstraction in the way, but the src is here .

Effectively we get a connection, call .create_adapter() and pass it to WebrenderSurfman::create().

This is a fork (not mine) of surfman anyway to allow getting the connection from the window handle.

But if surfman doesn't use GLES (on this platform) anyhow it's moot. I'm 99% sure the Gl implementation in this particular driver + hardware combo is broken. None of the servo/surfman demos work here, even with the recent winit upgrades

I'm using glutin successfully, so it's not an issue here and I can work around 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

No branches or pull requests

2 participants