Implement DRM backend

[shengwen-tw]

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]

Can I take on this issue?

[jserv]

Can I take on this issue?

Go ahead.

[huaxinliao]

I would also like to help solve this issue.

[jserv]

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]

drmu contains several nice programs for using DRM.

[jserv]

drmlist is a Linux program for direct interaction with Graphics Rendering devices, enabling:

• Connector & Mode Discovery: Listing available display connectors and rendering modes
• Direct Screen Rendering: Graphics rendering without X11/Wayland dependencies, using DRM device system calls