From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753995AbbIXMq0 (ORCPT ); Thu, 24 Sep 2015 08:46:26 -0400 Received: from down.free-electrons.com ([37.187.137.238]:59188 "EHLO mail.free-electrons.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752622AbbIXMqY (ORCPT ); Thu, 24 Sep 2015 08:46:24 -0400 Date: Thu, 24 Sep 2015 14:46:21 +0200 From: Thomas Petazzoni To: Tomi Valkeinen Cc: Greg Kroah-Hartman , linux-fbdev , DRI Development , Sudip Mukherjee , Teddy Wang , Noralf =?UTF-8?B?VHLDuG5uZXM=?= , Laurent Pinchart , Dave Airlie , Daniel Vetter , "linux-kernel@vger.kernel.org" , Arnaud Patard Subject: Re: No more new fbdev drivers, please Message-ID: <20150924144621.40e26f0a@free-electrons.com> In-Reply-To: <5603EC15.9090605@ti.com> References: <5603EC15.9090605@ti.com> Organization: Free Electrons X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.27; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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