-
Notifications
You must be signed in to change notification settings - Fork 58
GBM/KMS platform #42
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
Labels
Comments
DRM support could be neat, if it was also supported in winit or something else (I guess allowing only a single window, and using libinput for input events?). Are there currently any crates that provide |
|
notgull
added a commit
that referenced
this issue
Jul 15, 2023
This backend uses DUMB buffers to render to the CRTC. cc #42
Merged
notgull
added a commit
that referenced
this issue
Aug 12, 2023
This adds a DRM/KMS based backend to the system, as per #42. This system finds a CRTC and a connector, then uses that to create a frame buffer and a DUMB buffer that it can render to. There's much more to do, and is left as an exercise for anyone with a significant DRM-based use case to pick up and fix. Signed-off-by: John Nunley <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It may be useful to allow presenting CPU rendered buffers directly to the display on Linux.
raw-window-handle already supports GBM and DRM so it should be possible to use GBM or dumb buffers.
The text was updated successfully, but these errors were encountered: