From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: "Noralf Trønnes" <noralf@tronnes.org>,
linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>,
"Sudip Mukherjee" <sudipm.mukherjee@gmail.com>,
"Teddy Wang" <teddy.wang@siliconmotion.com>,
"Arnaud Patard" <arnaud.patard@rtp-net.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 3/3] staging: remove fbtft
Date: Thu, 24 Nov 2016 10:36:01 +0200 [thread overview]
Message-ID: <5e7ab2b5-b2bd-bf6f-c42b-33bbe00a024b@ti.com> (raw)
In-Reply-To: <60245ffa-0a64-cae0-7930-e05d92b35c09@tronnes.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 924 bytes --]
On 23/11/16 19:26, Noralf Trønnes wrote:
>
> Den 23.11.2016 09:03, skrev Tomi Valkeinen:
>> Since the fbdev framework is in maintenance mode and all new display
>> drivers should be made with the DRM framework, remove fbtft from
>> staging.
>>
>> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
>
> FYI:
> I'm working on a drm version of fbtft: https://github.com/notro/tinydrm
> I have just picked it up after a 4 month break.
>
> It is ready for a new review, except that I want to test how it would
> perform as a drm userspace driver first (for spi that would mean adding
> dma-buf support to spidev). If this performs well, then all the fbtft
> drivers could move to userspace. If it doesn't, then at least (very slow)
> i2c and e-ink displays could be userspace drivers.
Alright, sounds good to me.
So let's keep the staging fbdev drivers there until we have replacements.
Tomi
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-11-24 8:36 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 8:03 [RFC PATCH 0/3] staging: remove fbdev drivers Tomi Valkeinen
2016-11-23 8:03 ` [RFC PATCH 1/3] staging: remove xgifb Tomi Valkeinen
2016-11-23 8:03 ` [RFC PATCH 2/3] staging: remove sm750fb Tomi Valkeinen
2016-11-23 8:03 ` [RFC PATCH 3/3] staging: remove fbtft Tomi Valkeinen
2016-11-23 17:26 ` Noralf Trønnes
2016-11-24 8:36 ` Tomi Valkeinen [this message]
2016-11-23 20:12 ` Drew Fustini
2016-11-23 8:19 ` [RFC PATCH 0/3] staging: remove fbdev drivers Daniel Vetter
2016-11-23 8:21 ` Tomi Valkeinen
2016-11-23 8:25 ` Geert Uytterhoeven
2016-11-23 8:45 ` Daniel Vetter
2016-11-23 8:52 ` Greg Kroah-Hartman
2016-11-23 9:12 ` Tomi Valkeinen
2016-11-23 9:49 ` Greg Kroah-Hartman
2016-11-23 10:05 ` Thomas Petazzoni
2016-12-22 20:36 ` Andy Shevchenko
2016-12-08 22:00 ` Sudip Mukherjee
2016-12-08 1:01 ` Benjamin Herrenschmidt
2016-12-08 8:01 ` Tomi Valkeinen
2016-12-08 21:23 ` Benjamin Herrenschmidt
2016-12-08 21:43 ` Benjamin Herrenschmidt
2016-12-09 8:13 ` Daniel Vetter
2016-12-13 7:36 ` Gerd Hoffmann
2016-12-08 10:10 ` Daniel Vetter
2016-12-08 12:15 ` Geert Uytterhoeven
2016-12-08 14:02 ` Daniel Vetter
2016-12-08 14:22 ` Geert Uytterhoeven
2016-12-08 14:37 ` Thomas Petazzoni
2016-12-08 14:44 ` Geert Uytterhoeven
2016-12-08 15:21 ` Daniel Vetter
2016-12-08 21:34 ` Benjamin Herrenschmidt
2016-12-08 21:57 ` Benjamin Herrenschmidt
2016-12-09 8:34 ` Daniel Vetter
2016-12-09 8:41 ` Daniel Vetter
2016-12-09 11:48 ` Benjamin Herrenschmidt
2016-12-09 13:35 ` Daniel Vetter
2016-12-09 20:27 ` Benjamin Herrenschmidt
2016-12-13 7:18 ` Michel Dänzer
2016-12-09 11:44 ` Benjamin Herrenschmidt
2016-12-09 12:33 ` Geert Uytterhoeven
2016-12-09 13:19 ` Lucas Stach
2016-12-09 13:33 ` Daniel Vetter
2016-12-09 13:57 ` David Herrmann
2016-12-09 14:04 ` Daniel Vetter
2016-12-09 20:29 ` Benjamin Herrenschmidt
2016-12-09 8:30 ` Daniel Vetter
2016-12-08 14:59 ` Jani Nikula
2016-12-08 14:22 ` Daniel Vetter
2016-12-08 21:28 ` Benjamin Herrenschmidt
2016-12-09 0:08 ` Dave Airlie
2016-12-09 8:04 ` Geert Uytterhoeven
2016-12-09 11:40 ` Benjamin Herrenschmidt
2016-12-13 7:33 ` Gerd Hoffmann
2016-12-13 15:17 ` Laurent Pinchart
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=5e7ab2b5-b2bd-bf6f-c42b-33bbe00a024b@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=arnaud.patard@rtp-net.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=noralf@tronnes.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=teddy.wang@siliconmotion.com \
--cc=thomas.petazzoni@free-electrons.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