Make it compatible with a Wayland compositor

[matteodelabre]

[matteodelabre]

https://github.com/wayland-project/weston/blob/main/libweston/backend-fbdev/fbdev.c

[alistair23]

Hey! I wanted to check what the status of this is?

[matteodelabre]

Hi @alistair23! It’s high on my todo list, but I didn’t get time to work on waved recently. My plan is first to improve the performance of the frame generation loop and to then implement #4 along with this issue. I’ll make sure to update this issue when I get started on the implementation!

[tadfisher]

Would it not be a better option (in the long run) to get the mxsfb-drm driver running? That would give us a more modern driver to build upon, and more options for Wayland compositors (the popular ones don't have fbdev backends).

[alistair23]

I have support in the kernel, see alistair23/linux@6f96700

I think in the long run that would be a better option. It's probably not a bad idea to get waved working first with fbdev and then work on drm support after that.

[matteodelabre]

I may be missing something, but I can’t see the advantage in using mxsfb-drm. To clarify, when waved is fully operational, the stack will be as follows:

EPDC <> mxsfb <> waved <> Compositor <> User apps

So changing the underlying driver will only impact the interface that waved deals with, and won’t affect the Wayland compositors as far as I can see.

[alistair23]

I agree, I don't think it'll affect the compositor. It will make it easier to run a mainline kernel though as the current fbdev emulation isn't good enough to run Xoichtl