[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5e7ab2b5-b2bd-bf6f-c42b-33bbe00a024b@ti.com>
Date: Thu, 24 Nov 2016 10:36:01 +0200
From: Tomi Valkeinen <tomi.valkeinen@...com>
To: Noralf Trønnes <noralf@...nnes.org>,
<linux-fbdev@...r.kernel.org>, <dri-devel@...ts.freedesktop.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
Sudip Mukherjee <sudipm.mukherjee@...il.com>,
Teddy Wang <teddy.wang@...iconmotion.com>,
Arnaud Patard <arnaud.patard@...-net.org>
CC: <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH 3/3] staging: remove fbtft
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@...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
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists