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

Implement DRM backend #60

Open
shengwen-tw opened this issue Oct 9, 2024 · 5 comments
Open

Implement DRM backend #60

shengwen-tw opened this issue Oct 9, 2024 · 5 comments
Assignees

Comments

@shengwen-tw
Copy link
Collaborator

shengwen-tw commented Oct 9, 2024

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

@Bennctu
Copy link
Collaborator

Bennctu commented Oct 15, 2024

Can I take on this issue?

@jserv
Copy link
Contributor

jserv commented Oct 15, 2024

Can I take on this issue?

Go ahead.

@p96114175
Copy link

I would also like to help solve this issue.

@jserv
Copy link
Contributor

jserv commented Oct 31, 2024

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.

@jserv
Copy link
Contributor

jserv commented Nov 1, 2024

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
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

4 participants