From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Helge Deller <deller@gmx.de>, Daniel Vetter <daniel@ffwll.ch>,
Andy Shevchenko <andy@kernel.org>,
linux-fbdev@vger.kernel.org,
Michael Hennerich <michael.hennerich@analog.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Phillip Potter <phil@philpotter.co.uk>,
Carlis <zhangxuezhi1@yulong.com>,
Lee Jones <lee.jones@linaro.org>,
Heiner Kallweit <hkallweit1@gmail.com>
Subject: Re: [PATCH v1 1/4] fbtft: Unorphan the driver
Date: Wed, 26 Jan 2022 15:12:04 +0200 [thread overview]
Message-ID: <YfFIpBb7lL4ukWjm@smile.fi.intel.com> (raw)
In-Reply-To: <YfEv7OQs98O9wJdJ@kroah.com>
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
next prev parent reply other threads:[~2022-01-26 13:15 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 20:21 [PATCH v1 0/4] fbtft: Unorphan the driver for maintenance Andy Shevchenko
2022-01-25 20:21 ` [PATCH v1 1/4] fbtft: Unorphan the driver Andy Shevchenko
2022-01-26 8:31 ` Greg Kroah-Hartman
2022-01-26 10:31 ` Daniel Vetter
2022-01-26 11:17 ` Helge Deller
2022-01-26 11:26 ` Greg Kroah-Hartman
2022-01-26 13:12 ` Andy Shevchenko [this message]
2022-01-26 13:46 ` Javier Martinez Canillas
2022-01-26 14:08 ` Andy Shevchenko
2022-01-26 14:10 ` Andy Shevchenko
2022-01-26 14:15 ` Javier Martinez Canillas
2022-01-31 8:29 ` Javier Martinez Canillas
2022-01-31 9:18 ` Thomas Zimmermann
2022-01-31 10:18 ` Javier Martinez Canillas
2022-01-31 10:28 ` Thomas Zimmermann
2022-02-01 17:00 ` Geert Uytterhoeven
2022-02-01 17:06 ` Daniel Vetter
2022-02-01 19:00 ` Thomas Zimmermann
2022-01-31 11:36 ` Andy Shevchenko
2022-01-31 12:08 ` Javier Martinez Canillas
2022-01-31 13:23 ` Andy Shevchenko
2022-01-31 13:24 ` Andy Shevchenko
2022-01-31 13:55 ` Javier Martinez Canillas
2022-01-31 14:06 ` Andy Shevchenko
2022-01-26 17:34 ` Jani Nikula
2022-01-26 11:27 ` Daniel Vetter
2022-01-26 13:14 ` Andy Shevchenko
2022-01-26 11:31 ` Thomas Zimmermann
2022-01-26 13:13 ` Andy Shevchenko
2022-01-26 13:07 ` Andy Shevchenko
2022-01-26 13:06 ` Andy Shevchenko
2022-01-26 13:22 ` Daniel Stone
2022-01-25 20:21 ` [PATCH v1 2/4] fbtft: Move driver out from staging Andy Shevchenko
2022-01-25 20:21 ` [PATCH v1 3/4] fbtft: Kill outdated documentation Andy Shevchenko
2022-01-25 20:21 ` [PATCH v1 4/4] fbtft: Replace 'depends on FB_TFT' by 'if FB_TFT ... endif' Andy Shevchenko
2022-01-25 20:40 ` Randy Dunlap
2022-01-26 8:54 ` Joe Perches
2022-01-26 13:02 ` Andy Shevchenko
2022-01-26 8:52 ` [PATCH v1 0/4] fbtft: Unorphan the driver for maintenance Thomas Zimmermann
2022-01-26 10:02 ` Andy Shevchenko
2022-01-26 10:04 ` Andy Shevchenko
2022-01-26 10:28 ` Dan Carpenter
2022-01-26 12:37 ` Javier Martinez Canillas
2022-01-26 12:56 ` Greg Kroah-Hartman
2022-01-26 13:18 ` Andy Shevchenko
2022-01-26 13:44 ` Javier Martinez Canillas
2022-01-26 13:19 ` Javier Martinez Canillas
2022-01-26 13:36 ` Andy Shevchenko
2022-01-26 13:17 ` Andy Shevchenko
2022-01-26 10:43 ` Daniel Vetter
2022-01-26 10:47 ` Greg Kroah-Hartman
2022-01-26 10:52 ` Daniel Vetter
2022-01-26 11:15 ` Greg Kroah-Hartman
2022-01-26 13:26 ` Andy Shevchenko
2022-01-26 13:24 ` Andy Shevchenko
2022-01-26 10:59 ` Helge Deller
2022-01-26 11:18 ` Javier Martinez Canillas
2022-01-26 11:24 ` Daniel Vetter
2022-01-26 11:38 ` Helge Deller
2022-01-26 11:45 ` Sven Schnelle
2022-01-26 13:30 ` Andy Shevchenko
2022-01-27 9:18 ` Maxime Ripard
2022-01-26 11:31 ` Helge Deller
2022-01-26 11:38 ` Greg Kroah-Hartman
2022-01-26 11:51 ` Helge Deller
2022-01-26 12:15 ` Greg Kroah-Hartman
2022-01-26 11:51 ` Thomas Zimmermann
2022-01-26 13:27 ` Andy Shevchenko
2022-01-26 13:47 ` Javier Martinez Canillas
2022-01-26 14:11 ` Andy Shevchenko
2022-01-26 14:18 ` Javier Martinez Canillas
2022-01-26 14:24 ` Greg Kroah-Hartman
2022-01-26 14:45 ` Dan Carpenter
2022-01-26 22:31 ` Daniel Vetter
2022-01-27 6:29 ` Dan Carpenter
2022-01-27 10:32 ` Dmitry Vyukov
2022-01-27 11:11 ` Daniel Vetter
2022-01-27 16:34 ` Dmitry Vyukov
2022-01-26 22:37 ` Daniel Vetter
2022-01-26 11:41 ` Thomas Zimmermann
2022-01-26 13:32 ` Andy Shevchenko
2022-01-26 15:02 ` Thomas Zimmermann
2022-01-26 15:33 ` Andy Shevchenko
2022-01-26 15:54 ` Helge Deller
2022-01-26 13:15 ` Noralf Trønnes
2022-01-26 13:21 ` Andy Shevchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YfFIpBb7lL4ukWjm@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=andy@kernel.org \
--cc=daniel@ffwll.ch \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=hkallweit1@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=michael.hennerich@analog.com \
--cc=phil@philpotter.co.uk \
--cc=zhangxuezhi1@yulong.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).