From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomi Valkeinen Date: Thu, 24 Sep 2015 12:27:01 +0000 Subject: No more new fbdev drivers, please Message-Id: <5603EC15.9090605@ti.com> MIME-Version: 1 Content-Type: multipart/mixed; boundary="EhSr3wpUGubA9ipFD5RNT7K3rq4LxipCK" List-Id: To: Greg Kroah-Hartman , linux-fbdev , DRI Development Cc: Thomas Petazzoni , Teddy Wang , Daniel Vetter , "linux-kernel@vger.kernel.org" , Laurent Pinchart , Arnaud Patard , Dave Airlie , Sudip Mukherjee --EhSr3wpUGubA9ipFD5RNT7K3rq4LxipCK Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi all, 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". SM750 hardware seems to support multiple outputs, hardware overlays, 2D accelerator... I think it's pointless to write an fbdev driver for such a HW, as it's not possible to use those features with fbdev (without custom API). So, without spending too much time looking at those drivers, and without speaking to the authors, my initial suggestion is to remove them. Tomi --EhSr3wpUGubA9ipFD5RNT7K3rq4LxipCK Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWA+wVAAoJEPo9qoy8lh71CWkQAISiDT1paqqW9dcKO7Vzj4rR iFGxO0gv7oP1L7kP7vjZzNa6b5V+TXNBOZAmO1XAykJszo6Tr5Pez9duL+CeLEqB mcQARBtX00bV46Bnlsk7DcySf2L5LhgjVMxKM5TBqwiEH7dDxV9DVFkdZAImslfB neWesyZclEDtqxYELZEdRtFWeJcNvXj08YPrWv/2NPd9nR0w+O/dXxZ9qI/UnMjY CpzpUI/h/bzOPBdjT/96Gf+MQoKCgbPBcaaFYj4X+Fnc5WZ2498EnKp3sgiFC35o JOdicCXrTsyQFYzkbiTXEO3J79tknhT7xPqzNZZjWC+RMX1vE6tRTGYspZAzxVtd Kp1Da6wVTXRdzCHtiokqz/o4COnNsmFMMfw59RKIZYrcW1ywVvmahRWdVL2T4IYQ pRAWjvTRa0jQJ8/kLTZkOjwyq/Q+4XT2u3wM+NDHYpIY+y+mMlCSWh2Q2eJ7Lxci Vone4S4BOtmeFbHYqrmNOWXzty6WyTN8GH9JCMOIWjWICAE3RCculmpkZhE6wc80 qqyBYArrJH+Cw5XbdhoMSs9bYPEXAc7P8Hwtii0pNHe5rAOWUdWjgod4l7Ox+Qsd zp1sbUF3xg5LVinH3Xo+8b9PmljpP+EY9fckgy6WLLKADY+TMEK7yjSmqF18bkH9 zgyTlggewdOxhvfqcTbV =kOXm -----END PGP SIGNATURE----- --EhSr3wpUGubA9ipFD5RNT7K3rq4LxipCK-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomi Valkeinen Subject: No more new fbdev drivers, please Date: Thu, 24 Sep 2015 15:27:01 +0300 Message-ID: <5603EC15.9090605@ti.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1661733590==" Return-path: Received: from bear.ext.ti.com (bear.ext.ti.com [192.94.94.41]) by gabe.freedesktop.org (Postfix) with ESMTPS id C01C56EED2 for ; Thu, 24 Sep 2015 05:28:52 -0700 (PDT) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: Greg Kroah-Hartman , linux-fbdev , DRI Development Cc: Thomas Petazzoni , Teddy Wang , Daniel Vetter , "linux-kernel@vger.kernel.org" , Laurent Pinchart , Arnaud Patard , Dave Airlie , Sudip Mukherjee List-Id: dri-devel@lists.freedesktop.org --===============1661733590== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="EhSr3wpUGubA9ipFD5RNT7K3rq4LxipCK" --EhSr3wpUGubA9ipFD5RNT7K3rq4LxipCK Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi all, 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". SM750 hardware seems to support multiple outputs, hardware overlays, 2D accelerator... I think it's pointless to write an fbdev driver for such a HW, as it's not possible to use those features with fbdev (without custom API). So, without spending too much time looking at those drivers, and without speaking to the authors, my initial suggestion is to remove them. Tomi --EhSr3wpUGubA9ipFD5RNT7K3rq4LxipCK Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWA+wVAAoJEPo9qoy8lh71CWkQAISiDT1paqqW9dcKO7Vzj4rR iFGxO0gv7oP1L7kP7vjZzNa6b5V+TXNBOZAmO1XAykJszo6Tr5Pez9duL+CeLEqB mcQARBtX00bV46Bnlsk7DcySf2L5LhgjVMxKM5TBqwiEH7dDxV9DVFkdZAImslfB neWesyZclEDtqxYELZEdRtFWeJcNvXj08YPrWv/2NPd9nR0w+O/dXxZ9qI/UnMjY CpzpUI/h/bzOPBdjT/96Gf+MQoKCgbPBcaaFYj4X+Fnc5WZ2498EnKp3sgiFC35o JOdicCXrTsyQFYzkbiTXEO3J79tknhT7xPqzNZZjWC+RMX1vE6tRTGYspZAzxVtd Kp1Da6wVTXRdzCHtiokqz/o4COnNsmFMMfw59RKIZYrcW1ywVvmahRWdVL2T4IYQ pRAWjvTRa0jQJ8/kLTZkOjwyq/Q+4XT2u3wM+NDHYpIY+y+mMlCSWh2Q2eJ7Lxci Vone4S4BOtmeFbHYqrmNOWXzty6WyTN8GH9JCMOIWjWICAE3RCculmpkZhE6wc80 qqyBYArrJH+Cw5XbdhoMSs9bYPEXAc7P8Hwtii0pNHe5rAOWUdWjgod4l7Ox+Qsd zp1sbUF3xg5LVinH3Xo+8b9PmljpP+EY9fckgy6WLLKADY+TMEK7yjSmqF18bkH9 zgyTlggewdOxhvfqcTbV =kOXm -----END PGP SIGNATURE----- --EhSr3wpUGubA9ipFD5RNT7K3rq4LxipCK-- --===============1661733590== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============1661733590==-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755598AbbIXM3H (ORCPT ); Thu, 24 Sep 2015 08:29:07 -0400 Received: from bear.ext.ti.com ([192.94.94.41]:52665 "EHLO bear.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754252AbbIXM3E (ORCPT ); Thu, 24 Sep 2015 08:29:04 -0400 To: Greg Kroah-Hartman , linux-fbdev , DRI Development CC: Sudip Mukherjee , Teddy Wang , Thomas Petazzoni , =?UTF-8?Q?Noralf_Tr=c3=b8nnes?= , Laurent Pinchart , Dave Airlie , Daniel Vetter , "linux-kernel@vger.kernel.org" , Arnaud Patard From: Tomi Valkeinen Subject: No more new fbdev drivers, please X-Enigmail-Draft-Status: N1110 Message-ID: <5603EC15.9090605@ti.com> Date: Thu, 24 Sep 2015 15:27:01 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="EhSr3wpUGubA9ipFD5RNT7K3rq4LxipCK" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --EhSr3wpUGubA9ipFD5RNT7K3rq4LxipCK Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi all, 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". SM750 hardware seems to support multiple outputs, hardware overlays, 2D accelerator... I think it's pointless to write an fbdev driver for such a HW, as it's not possible to use those features with fbdev (without custom API). So, without spending too much time looking at those drivers, and without speaking to the authors, my initial suggestion is to remove them. Tomi --EhSr3wpUGubA9ipFD5RNT7K3rq4LxipCK Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWA+wVAAoJEPo9qoy8lh71CWkQAISiDT1paqqW9dcKO7Vzj4rR iFGxO0gv7oP1L7kP7vjZzNa6b5V+TXNBOZAmO1XAykJszo6Tr5Pez9duL+CeLEqB mcQARBtX00bV46Bnlsk7DcySf2L5LhgjVMxKM5TBqwiEH7dDxV9DVFkdZAImslfB neWesyZclEDtqxYELZEdRtFWeJcNvXj08YPrWv/2NPd9nR0w+O/dXxZ9qI/UnMjY CpzpUI/h/bzOPBdjT/96Gf+MQoKCgbPBcaaFYj4X+Fnc5WZ2498EnKp3sgiFC35o JOdicCXrTsyQFYzkbiTXEO3J79tknhT7xPqzNZZjWC+RMX1vE6tRTGYspZAzxVtd Kp1Da6wVTXRdzCHtiokqz/o4COnNsmFMMfw59RKIZYrcW1ywVvmahRWdVL2T4IYQ pRAWjvTRa0jQJ8/kLTZkOjwyq/Q+4XT2u3wM+NDHYpIY+y+mMlCSWh2Q2eJ7Lxci Vone4S4BOtmeFbHYqrmNOWXzty6WyTN8GH9JCMOIWjWICAE3RCculmpkZhE6wc80 qqyBYArrJH+Cw5XbdhoMSs9bYPEXAc7P8Hwtii0pNHe5rAOWUdWjgod4l7Ox+Qsd zp1sbUF3xg5LVinH3Xo+8b9PmljpP+EY9fckgy6WLLKADY+TMEK7yjSmqF18bkH9 zgyTlggewdOxhvfqcTbV =kOXm -----END PGP SIGNATURE----- --EhSr3wpUGubA9ipFD5RNT7K3rq4LxipCK--