-
-
Notifications
You must be signed in to change notification settings - Fork 629
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
Test with Gokrazy #841
Comments
http://seenaburns.com/2018/04/04/writing-to-the-framebuffer/
|
IIRC, The Pi has OpenGL ES 2.0 and can be used without even having to run under X Windows. The GL context is setup using straight EGL . See https://stackoverflow.com/questions/16080639/create-opengl-context-in-linux-consoleraspbian. The VideoCore sdk mentioned is installed by default in raspbian. Also it seems to be working with GLFW (don't know about console mode though): https://github.com/libretro/ludo |
Thank you for the information! |
You're welcome ! After a bit of digging, looks like GLFW uses Xlib for input regardless of the context creation API. So supporting the Pi without running X11 will require an EGL wrapper + custom input handling 😢 |
For Pi, I thought we could use DispmanX (#760). I'm not sure this supports inputs though. |
The examples have custom keyboard handling code. Short version: change terminal attributes and read stdin. But... There's always the good old SDL2 which works on Pi without X. Added bonus: you can test the SDL2 driver on desktop! |
Input handling from /dev/input/* devices is easy enough, I do it for joysticks already. |
https://gokrazy.org/
I'm not sure how graphics driver should be implemented.
The text was updated successfully, but these errors were encountered: