Support Linux DRM backend #69
Conversation
What compatibility risks exist when using DRM legacy interfaces with newer Linux kernels? Could you verify the compatibility status of libdrm across different kernel versions? What prevents the DRM backend from rendering content across the full screen resolution? |
|
@a1091150, You might check DRM backend for your environment as well. |
|
|
||
| return true; | ||
|
|
||
| bail_crtc: |
There was a problem hiding this comment.
I'm confused about this. It should be as below.
/* Retrieve resources */
if (!get_resources(tx->drm_dri_fd, &RES(tx)))
goto bail_res;
....
bail_fb:
drmModeRmFB(tx->drm_dri_fd, tx->fb_id);
munmap(tx->fb_base, tx->fb_len);
bail_crtc:
drmModeFreeCrtc(CRTC(tx));
bail_conn:
drmModeFreeConnector(CONN(tx));
bail_res:
drmModeFreeResources(RES(tx));
I need more time to research and adjust. |
|
Check the DRM implementation for reference: https://github.com/zlgopen/awtk-linux-fb/blob/master/awtk-port/lcd_linux/lcd_linux_drm.c |
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
|
|
||
| /* Register the Linux DRM backend */ | ||
|
|
||
| const twin_backend_t g_twin_backend = { |
There was a problem hiding this comment.
You should add poll operation as it is required in recent main branch.
There was a problem hiding this comment.
As the original implementation, we creates another thread to handle the events in function twin_linux_evdev_thread. So do you suggest refactoring linux_input.c#L255~278?
Or we just assign NULL to .poll?
/* Register the Linux DRM backend */
const twin_backend_t g_twin_backend = {
.init = twin_drm_init,
.poll = NULL, /*without implementation*/
.configure = twin_drm_configure,
.exit = twin_drm_exit,
};There was a problem hiding this comment.
@alanjian85, can you comment this?
| $ sudo ./demo-drm | ||
| ``` | ||
|
|
||
| The DRM device can be assigened via the environment variable `DRI_CARD`. |
There was a problem hiding this comment.
DRI_CARD is not common for understanding. How about DRMDEVICE?
Currently, using the DRM legacy interface is suitable for Mado's backend because we only need basic window display without advanced features.