Messages in this thread | | | From | Andy Shevchenko <> | Date | Wed, 26 Jan 2022 12:02:36 +0200 | Subject | Re: [PATCH v1 0/4] fbtft: Unorphan the driver for maintenance |
| |
On Wed, Jan 26, 2022 at 10:52 AM Thomas Zimmermann <tzimmermann@suse.de> wrote: > > Hi > > Am 25.01.22 um 21:21 schrieb Andy Shevchenko: > > Since we got a maintainer for fbdev, I would like to > > unorphan fbtft (with the idea of sending PRs to Helge) > > and move it out of staging since there is no more clean > > up work expected and no more drivers either. > > > > Thoughts?
Thanks for sharing yours, my answers below.
> But why? We already have DRM drivers for some of these devices.
No, we do not (only a few are available).
> Porting > the others to DRM is such a better long-term plan. OTOH, as no one has > shown up and converted them, maybe they should be left dead or removed > entirely.
As I mentioned above there are devices that nobody will take time to port to a way too complex DRM subsystem. But the devices are cheap and quite widespread in the embedded world. I'm in possession of 3 or 4 different models and only 1 is supported by tiny DRM.
On top of that the subtle fact people forgot about FBTFT is that it does support parallel interface (yes, I know that it's not performant, but one of the displays I have is with that type of interface).
P.S. For the record, I will personally NAK any attempts to remove that driver from the kernel. And this is another point why it's better not to be under the staging.
-- With Best Regards, Andy Shevchenko
| |