linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	linux-fbdev <linux-fbdev@vger.kernel.org>,
	"DRI Development" <dri-devel@lists.freedesktop.org>,
	"Sudip Mukherjee" <sudipm.mukherjee@gmail.com>,
	"Teddy Wang" <teddy.wang@siliconmotion.com>,
	"Noralf Trønnes" <noralf@tronnes.org>,
	"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
	"Dave Airlie" <airlied@redhat.com>,
	"Daniel Vetter" <daniel.vetter@ffwll.ch>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Arnaud Patard" <apatard@mandriva.com>
Subject: Re: No more new fbdev drivers, please
Date: Thu, 24 Sep 2015 12:46:21 +0000	[thread overview]
Message-ID: <20150924144621.40e26f0a@free-electrons.com> (raw)
In-Reply-To: <5603EC15.9090605@ti.com>

Hello,

On Thu, 24 Sep 2015 15:27:01 +0300, Tomi Valkeinen wrote:

> fbdev is (more or less) maintained, but it's a deprecated framework. All
> new Linux display drivers should be done on DRM.
> 
> So let's not add any more new fbdev drivers.
> 
> I will continue to maintain the current fbdev drivers, and I don't mind
> adding some new features to those current drivers, as long as the amount
> of code required to add the features stays sensible.
> 
> I see we have three fbdev drivers in staging: xgifb, fbtft and sm750fb,
> and the question is what to do with those.
> 
> xgifb was added in 2010, and is still in staging.
> 
> fbtft looks like maybe some kind of framework on top of fbdev, with
> fbtft specific subdrivers... I didn't look at it in detail, but my gut
> says "never".

fbtft mainly drives some very simple I2C-based or SPI-based displays,
and DRM is I believe overkill for such displays. Last time I talked
with Laurent Pinchart about such drivers, I believe he said that such
simple drivers could probably continue to use the fbdev subsystem.

Or are there some plans to make the writing of DRM drivers for very
simple/trivial devices a bit simpler?

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-09-24 12:46 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24 12:27 No more new fbdev drivers, please Tomi Valkeinen
2015-09-24 12:46 ` Thomas Petazzoni [this message]
2015-09-24 15:21   ` Austin S Hemmelgarn
2015-09-24 15:38     ` Alex Deucher
2015-09-24 15:59     ` Daniel Vetter
2015-09-24 16:17       ` Austin S Hemmelgarn
2015-09-24 17:12       ` Ondrej Zary
2015-09-24 18:05         ` Daniel Vetter
2015-09-24 15:23   ` Daniel Vetter
2015-09-26  8:28     ` Geert Uytterhoeven
2015-09-26 17:07       ` Alex Deucher
2015-09-26 18:01         ` Geert Uytterhoeven
2015-09-26 18:13           ` David Herrmann
2015-09-26 18:46             ` Geert Uytterhoeven
2015-09-26 20:49               ` Rob Clark
2015-09-26 21:55                 ` Dave Airlie
2015-09-30 11:59               ` Emil Velikov
2015-09-28  7:39             ` Gerd Hoffmann
2015-09-28 12:36               ` Daniel Vetter
2015-09-29  8:23                 ` Gerd Hoffmann
2015-09-29  8:33                   ` Laurent Pinchart
2015-09-28 20:56           ` Bernie Thompson
     [not found]           ` <CAF1V4O_9LC9QM_AcE7gaV4hp4jcEe47nzKj=CXxvsnH_L=YRYw@mail.gmail.com>
2015-09-29  7:05             ` Daniel Vetter
2015-09-25  8:49 ` Aaro Koskinen
2015-09-25 11:00   ` Ondrej Zary
2015-09-25 10:41 ` Kamil Lulko
2015-09-25 13:09   ` Tomi Valkeinen
2015-09-25 18:44     ` Daniel Vetter
2015-09-26  9:03   ` Geert Uytterhoeven
2015-09-26  7:27 ` Sudip Mukherjee
2015-09-26  7:29   ` Ilia Mirkin
2015-09-27 13:09 ` Noralf Trønnes
2015-09-27 16:08   ` Emil Velikov
2015-09-28 22:51     ` Noralf Trønnes
2015-09-29  7:07       ` Daniel Vetter

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=20150924144621.40e26f0a@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=airlied@redhat.com \
    --cc=apatard@mandriva.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --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=tomi.valkeinen@ti.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).