[Question] Failed to create framebuffer about drm-rs HOT 4 CLOSED

@Drakulix Noticed the same while updating my toy project to develop and trying to understand why the previous implementation passed 32 for both fields (through fn bpp() and fn depth()), passing 32 indeed fixes the error (here and in legacy_modeset, atomic_modeset).

from drm-rs.

Well, I am not sure if depth or bpp values of "1" are actually valid.

Can you try chaging the arguments of add_framebuffer in kms-interactive to something more reasonable like &db, 32, 32? That might fix it.

from drm-rs.

Then please someone make a PR and fix the examples 😅 .
For a correct mapping between color-formats and bpp/depth, we would need to maintain a table ourselves, which I would rather not do (drm-fourcc has a lot of formats). (Which is why depth() and bpp() were dropped.)

But that should not be an issue of the examples, as they always use a hard-coded format. So we should just set the example to correct values for the given color format.

from drm-rs.

Closed via #85

from drm-rs.