Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1529062
| From | Tomi Valkeinen <tomi.valkeinen@ti.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFC PATCH 3/3] staging: remove fbtft |
| Date | 2016-11-24 09:40 +0100 |
| Message-ID | <sGXJv-fi-7@gated-at.bofh.it> (permalink) |
| References | <sGAMV-2jc-3@gated-at.bofh.it> <sGAMV-2jc-17@gated-at.bofh.it> <sGJGy-7OY-31@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
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
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[RFC PATCH 3/3] staging: remove fbtft Tomi Valkeinen <tomi.valkeinen@ti.com> - 2016-11-23 09:10 +0100
Re: [RFC PATCH 3/3] staging: remove fbtft Noralf Trønnes <noralf@tronnes.org> - 2016-11-23 18:40 +0100
Re: [RFC PATCH 3/3] staging: remove fbtft Tomi Valkeinen <tomi.valkeinen@ti.com> - 2016-11-24 09:40 +0100
Re: [RFC PATCH 3/3] staging: remove fbtft Drew Fustini <drew@pdp7.com> - 2016-11-23 21:20 +0100
csiph-web