Thread (85 messages) 85 messages, 16 authors, 2022-02-01

Re: [PATCH v1 1/4] fbtft: Unorphan the driver

From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date: 2022-01-26 13:08:05
Also in: dri-devel, linux-staging, lkml

On Wed, Jan 26, 2022 at 11:31:45AM +0100, Daniel Vetter wrote:
On Wed, Jan 26, 2022 at 9:31 AM Greg Kroah-Hartman
[off-list ref] wrote:
quoted
On Tue, Jan 25, 2022 at 10:21:14PM +0200, Andy Shevchenko wrote:
...
quoted
I'm ok with the files moving if the dri developers agree with it.  It's
up to them, not me.
On one hand I'm happy anytime someone volunteers to help out.

On the other hand ... why does it have to be resurrecting fbdev?
There's an entire community of people who really know graphics and
display and spent considerable amount of effort on creating useful and
documented helpers for pretty much anything you might ever want to do.
Why nobody has converted these drivers to be DRM based?

For all these years no new conversion happens except couple, which
I don't even have a hardware to see. But I have the hardware that
is supported exclusively by fbtft driver.
And somehow we have to go back to typing out things the hard way, with
full verbosity, for an uapi that distros are abandoning (e.g. even for
sdl the direction is to run it on top of drm with a compat layer,
afaiui fedora is completely ditching any userspace that still even
uses /dev/fb/0). And yes I know there's still some gaps in drm,
largely for display features which were really en vogue about 20 years
ago. And we're happy to add that support, if someone who still has
such hardware can put in the little bit of work needed ...

I don't get this.
I don't get how Fedora is related here.

It's not useful to bury the /dev/fbX out for the devices that
the use of are black-and-white output on small embedded systems.


-- 
With Best Regards,
Andy Shevchenko

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help