[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YfFIpBb7lL4ukWjm@smile.fi.intel.com>
Date: Wed, 26 Jan 2022 15:12:04 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Helge Deller <deller@....de>, Daniel Vetter <daniel@...ll.ch>,
Andy Shevchenko <andy@...nel.org>, linux-fbdev@...r.kernel.org,
Michael Hennerich <michael.hennerich@...log.com>,
linux-staging@...ts.linux.dev, linux-kernel@...r.kernel.org,
dri-devel@...ts.freedesktop.org,
Phillip Potter <phil@...lpotter.co.uk>,
Carlis <zhangxuezhi1@...ong.com>,
Lee Jones <lee.jones@...aro.org>,
Heiner Kallweit <hkallweit1@...il.com>
Subject: Re: [PATCH v1 1/4] fbtft: Unorphan the driver
On Wed, Jan 26, 2022 at 12:26:36PM +0100, Greg Kroah-Hartman wrote:
> On Wed, Jan 26, 2022 at 12:17:08PM +0100, Helge Deller wrote:
> > On 1/26/22 11:31, Daniel Vetter wrote:
...
> > You are describing a transitioning over to DRM - which is Ok.
> > But on that way there is no need to ignore, deny or even kill usage scenarios
> > which are different compared to your usage scenarios (e.g. embedded devices,
> > old platforms, slow devices, slow busses, no 3D hardware features,
> > low-color devices, ...).
>
> All of those should be handled by the drm layer, as Daniel keeps
> pointing out. If not, then the tinydrm layer needs to be enhanced to do
> so.
>
> Anyone have a pointer to hardware I can buy that is one of these fbtft
> drivers that I could do a port to drm to see just how much work is
> really needed here?
I have bought myself (for other purposes, I mean not to convert the driver(s))
SSD1306 based display (SPI), SSD1331 (SPI), HX88347d (parallel).
Each of them costed less than $10 with delivery to EU (nowadays maybe a bit
more expensive). I believe it's very easy to find the links on AliExpress.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists