Helge Deller <deller@xxxxxx> writes: > On 1/26/22 12:24, Daniel Vetter wrote: >> And that point was about 5 years ago, and has been discussed at some >> plumbers meanwhile, resulting in the staging TODO patches to make >> these drm drivers to destage them. >> >> Fixing bugs in fbdev is all fine, reopening it for merging new drivers is not. > > We are on the same page! > I'm not at all proposing to include new drivers for (relatively) new > hardware into fbdev, which is capable to be written as DRM driver. In my opinion that should be decided depending on the main usecase: If it's X11 or similar, it should go to DRM. If its main use case is kernel text console, it should go to fbdev. I think the main concern/trouble about fbdev is the userspace interface, and i personally would be totally fine seeing that go away (except the ability to change video mode with fbset). For me its important as kernel console for old systems, and don't want to run X11 on them. Given the ongoing discussion about performance and drm, i don't expect DRM gaining HW acceleration capabilities for text consoles. So i think both should exist, just for different usecases.
