Implement DRM backend #60
Assignees
Comments
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
I would also like to help solve this issue. |
To proceed, start with the Linux framebuffer backend. For example, build Mado on a Raspberry Pi and run it without the X Window System. You may encounter some unexpected behavior, which will provide an opportunity to make your own contributions. Later, when working with the DRM/KMS driver, you can build on the knowledge gained from the Linux framebuffer backend. |
|
drmu contains several nice programs for using DRM. |
Bennctu
added a commit
to Bennctu/mado
that referenced
this issue
Nov 3, 2024
Implemented DRM-based framebuffer setup, including: - Opening DRM device - Creating the dumb buffer and mapping it to framebuffer - Setting mode and handling CRTC for connected display output Currently, using the DRM legacy interface is suitable for Mado's backend if we only need basic window display without advanced features. The DRM legacy is simpler to implement. Close sysprog21#60
Bennctu
added a commit
to Bennctu/mado
that referenced
this issue
Nov 6, 2024
Implemented DRM-based framebuffer setup, including: - Opening DRM device - Creating dumb buffers and mapping them to framebuffers - Setting mode and handling CRTC for connected display output Currently, using the DRM legacy interface is suitable for Mado's backend if we only need basic window display without advanced features. The DRM legacy is simpler to implement. Close sysprog21#60
|
drmlist is a Linux program for direct interaction with Graphics Rendering devices, enabling:
|
Bennctu
added a commit
to Bennctu/mado
that referenced
this issue
Nov 23, 2024
Implemented DRM-based framebuffer setup, including: - Opening DRM device - Creating dumb buffers and mapping them to framebuffers - Setting mode and handling CRTC for connected display output Currently, using the DRM legacy interface is suitable for Mado's backend if we only need basic window display without advanced features. The DRM legacy is simpler to implement. Close sysprog21#60
Bennctu
added a commit
to Bennctu/mado
that referenced
this issue
Nov 23, 2024
Implemented DRM-based framebuffer setup, including: - Opening DRM device - Creating dumb buffers and mapping them to framebuffers - Setting mode and handling CRTC for connected display output Currently, using the DRM legacy interface is suitable for Mado's backend if we only need basic window display without advanced features. The DRM legacy is simpler to implement. Close sysprog21#60
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Linux Framebuffer Device (fbdev) is an older graphics interface in Linux, serving as a simple abstraction for a display framebuffer in memory. However, it offers limited functionality compared to DRM (Direct Rendering Manager).
In contrast, DRM provides a unified and consistent API for managing graphics devices, including support for multiple displays and GPUs. It allows for advanced display configuration, such as setting resolution, color depth, and other display modes.
Check also #3
The text was updated successfully, but these errors were encountered: