On 5/11/23 15:10, Geert Uytterhoeven wrote:

Hi Helge,

On Thu, May 11, 2023 at 3:05 PM Helge Deller [off-list ref] wrote:

quoted

On 5/11/23 09:55, Thomas Zimmermann wrote:

quoted

But the work I do within fbdev is mostly for improving DRM.

Sure.

quoted

For the
other issues in this file, I don't think that matroxfb should even be
around any longer. Fbdev has been deprecated for a long time. But a
small number of drivers are still in use and we still need its
framebuffer console. So someone should either put significant effort
into maintaining fbdev, or it should be phased out. But neither is
happening.

You're wrong.

You don't mention that for most older machines DRM isn't an acceptable
way to go due to it's limitations, e.g. it's low-speed due to missing
2D-acceleration for older cards and and it's incapability to change screen
resolution at runtime (just to name two of the bigger limitations here).
So, unless we somehow find a good way to move such drivers over to DRM
(with a set of minimal 2D acceleration), they are still important.

DRM can change resolution at runtime,

Right, sure.

just not through the fbdev API.

... and sadly the simpledrm-based drivers neither.

Or do you mean the resolution of the text console, akin to
"fbset <mode>"?

yes.

I have to admit I do not know if there is a command
line tool to do that...

Helge