From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Tomi Valkeinen" <tomi.valkeinen@ti.com>,
linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>,
"Noralf Trønnes" <noralf@tronnes.org>,
"Sudip Mukherjee" <sudipm.mukherjee@gmail.com>,
"Teddy Wang" <teddy.wang@siliconmotion.com>,
"Arnaud Patard" <arnaud.patard@rtp-net.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/3] staging: remove fbdev drivers
Date: Thu, 08 Dec 2016 01:01:19 +0000 [thread overview]
Message-ID: <1481158879.26959.41.camel@kernel.crashing.org> (raw)
In-Reply-To: <1479888193-23908-1-git-send-email-tomi.valkeinen@ti.com>
On Wed, 2016-11-23 at 10:03 +0200, Tomi Valkeinen wrote:
> Hi,
>
> Since the fbdev framework is in maintenance mode and all new display drivers
> should be made with the DRM framework, remove the fbdev drivers from staging.
>
> Note: the patches are created with git format-patch -D, so they can't be
> applied. Only for review.
I missed the discussion where this decision was made, I admit I am
unimpressed by it.
DRM drivers don't strike me as suitable for small/slow cores with dumb
framebuffers or simple 2D only accel, such as the one found in the ASpeed
BMCs.
With drmfb you basically have to shadow everything into memory & copy
over everything, and locks you out of simple 2D accel. For a simple text
console the result is orders of magnitude slower and memory hungry than
a simple fbdev.
At least that was the case last I looked at the DRM stuff with Dave,
maybe things have changed...
Not everything has a powerful 3D GPU.
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Tomi Valkeinen" <tomi.valkeinen@ti.com>,
linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>,
"Noralf Trønnes" <noralf@tronnes.org>,
"Sudip Mukherjee" <sudipm.mukherjee@gmail.com>,
"Teddy Wang" <teddy.wang@siliconmotion.com>,
"Arnaud Patard" <arnaud.patard@rtp-net.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/3] staging: remove fbdev drivers
Date: Thu, 08 Dec 2016 12:01:19 +1100 [thread overview]
Message-ID: <1481158879.26959.41.camel@kernel.crashing.org> (raw)
In-Reply-To: <1479888193-23908-1-git-send-email-tomi.valkeinen@ti.com>
On Wed, 2016-11-23 at 10:03 +0200, Tomi Valkeinen wrote:
> Hi,
>
> Since the fbdev framework is in maintenance mode and all new display drivers
> should be made with the DRM framework, remove the fbdev drivers from staging.
>
> Note: the patches are created with git format-patch -D, so they can't be
> applied. Only for review.
I missed the discussion where this decision was made, I admit I am
unimpressed by it.
DRM drivers don't strike me as suitable for small/slow cores with dumb
framebuffers or simple 2D only accel, such as the one found in the ASpeed
BMCs.
With drmfb you basically have to shadow everything into memory & copy
over everything, and locks you out of simple 2D accel. For a simple text
console the result is orders of magnitude slower and memory hungry than
a simple fbdev.
At least that was the case last I looked at the DRM stuff with Dave,
maybe things have changed...
Not everything has a powerful 3D GPU.
Ben.
next prev parent reply other threads:[~2016-12-08 1:01 UTC|newest]
Thread overview: 154+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 8:03 [RFC PATCH 0/3] staging: remove fbdev drivers Tomi Valkeinen
2016-11-23 8:03 ` Tomi Valkeinen
2016-11-23 8:03 ` Tomi Valkeinen
2016-11-23 8:03 ` [RFC PATCH 1/3] staging: remove xgifb Tomi Valkeinen
2016-11-23 8:03 ` Tomi Valkeinen
2016-11-23 8:03 ` Tomi Valkeinen
2016-11-23 8:03 ` [RFC PATCH 2/3] staging: remove sm750fb Tomi Valkeinen
2016-11-23 8:03 ` Tomi Valkeinen
2016-11-23 8:03 ` Tomi Valkeinen
2016-11-23 8:03 ` [RFC PATCH 3/3] staging: remove fbtft Tomi Valkeinen
2016-11-23 8:03 ` Tomi Valkeinen
2016-11-23 8:03 ` Tomi Valkeinen
2016-11-23 17:26 ` Noralf Trønnes
2016-11-23 17:26 ` Noralf Trønnes
2016-11-23 17:26 ` Noralf Trønnes
2016-11-24 8:36 ` Tomi Valkeinen
2016-11-24 8:36 ` Tomi Valkeinen
2016-11-24 8:36 ` Tomi Valkeinen
2016-11-23 20:12 ` Drew Fustini
2016-11-23 20:12 ` Drew Fustini
2016-11-23 8:19 ` [RFC PATCH 0/3] staging: remove fbdev drivers Daniel Vetter
2016-11-23 8:19 ` Daniel Vetter
2016-11-23 8:19 ` Daniel Vetter
2016-11-23 8:21 ` Tomi Valkeinen
2016-11-23 8:21 ` Tomi Valkeinen
2016-11-23 8:25 ` Geert Uytterhoeven
2016-11-23 8:25 ` Geert Uytterhoeven
2016-11-23 8:25 ` Geert Uytterhoeven
2016-11-23 8:45 ` Daniel Vetter
2016-11-23 8:45 ` Daniel Vetter
2016-11-23 8:45 ` Daniel Vetter
2016-11-23 8:52 ` Greg Kroah-Hartman
2016-11-23 8:52 ` Greg Kroah-Hartman
2016-11-23 8:52 ` Greg Kroah-Hartman
2016-11-23 9:12 ` Tomi Valkeinen
2016-11-23 9:12 ` Tomi Valkeinen
2016-11-23 9:12 ` Tomi Valkeinen
2016-11-23 9:49 ` Greg Kroah-Hartman
2016-11-23 9:49 ` Greg Kroah-Hartman
2016-11-23 9:49 ` Greg Kroah-Hartman
2016-11-23 10:05 ` Thomas Petazzoni
2016-11-23 10:05 ` Thomas Petazzoni
2016-12-22 20:36 ` Andy Shevchenko
2016-12-22 20:36 ` Andy Shevchenko
2016-12-22 20:36 ` Andy Shevchenko
2016-12-08 22:00 ` Sudip Mukherjee
2016-12-08 22:00 ` Sudip Mukherjee
2016-12-08 22:00 ` Sudip Mukherjee
2016-12-08 1:01 ` Benjamin Herrenschmidt [this message]
2016-12-08 1:01 ` Benjamin Herrenschmidt
2016-12-08 8:01 ` Tomi Valkeinen
2016-12-08 8:01 ` Tomi Valkeinen
2016-12-08 8:01 ` Tomi Valkeinen
2016-12-08 21:23 ` Benjamin Herrenschmidt
2016-12-08 21:23 ` Benjamin Herrenschmidt
2016-12-08 21:23 ` Benjamin Herrenschmidt
2016-12-08 21:43 ` Benjamin Herrenschmidt
2016-12-08 21:43 ` Benjamin Herrenschmidt
2016-12-08 21:43 ` Benjamin Herrenschmidt
2016-12-09 8:13 ` Daniel Vetter
2016-12-09 8:13 ` Daniel Vetter
2016-12-09 8:13 ` Daniel Vetter
2016-12-13 7:36 ` Gerd Hoffmann
2016-12-13 7:36 ` Gerd Hoffmann
2016-12-08 10:10 ` Daniel Vetter
2016-12-08 10:10 ` Daniel Vetter
2016-12-08 10:10 ` Daniel Vetter
2016-12-08 12:15 ` Geert Uytterhoeven
2016-12-08 12:15 ` Geert Uytterhoeven
2016-12-08 12:15 ` Geert Uytterhoeven
2016-12-08 14:02 ` Daniel Vetter
2016-12-08 14:02 ` Daniel Vetter
2016-12-08 14:02 ` Daniel Vetter
2016-12-08 14:22 ` Geert Uytterhoeven
2016-12-08 14:22 ` Geert Uytterhoeven
2016-12-08 14:37 ` Thomas Petazzoni
2016-12-08 14:37 ` Thomas Petazzoni
2016-12-08 14:44 ` Geert Uytterhoeven
2016-12-08 14:44 ` Geert Uytterhoeven
2016-12-08 14:44 ` Geert Uytterhoeven
2016-12-08 15:21 ` Daniel Vetter
2016-12-08 15:21 ` Daniel Vetter
2016-12-08 15:21 ` Daniel Vetter
2016-12-08 21:34 ` Benjamin Herrenschmidt
2016-12-08 21:34 ` Benjamin Herrenschmidt
2016-12-08 21:34 ` Benjamin Herrenschmidt
2016-12-08 21:57 ` Benjamin Herrenschmidt
2016-12-08 21:57 ` Benjamin Herrenschmidt
2016-12-08 21:57 ` Benjamin Herrenschmidt
2016-12-09 8:34 ` Daniel Vetter
2016-12-09 8:34 ` Daniel Vetter
2016-12-09 8:34 ` Daniel Vetter
2016-12-09 8:41 ` Daniel Vetter
2016-12-09 8:41 ` Daniel Vetter
2016-12-09 8:41 ` Daniel Vetter
2016-12-09 11:48 ` Benjamin Herrenschmidt
2016-12-09 11:48 ` Benjamin Herrenschmidt
2016-12-09 11:48 ` Benjamin Herrenschmidt
2016-12-09 13:35 ` Daniel Vetter
2016-12-09 13:35 ` Daniel Vetter
2016-12-09 13:35 ` Daniel Vetter
2016-12-09 20:27 ` Benjamin Herrenschmidt
2016-12-09 20:27 ` Benjamin Herrenschmidt
2016-12-09 20:27 ` Benjamin Herrenschmidt
2016-12-13 7:18 ` Michel Dänzer
2016-12-13 7:18 ` Michel Dänzer
2016-12-13 7:18 ` Michel Dänzer
2016-12-09 11:44 ` Benjamin Herrenschmidt
2016-12-09 11:44 ` Benjamin Herrenschmidt
2016-12-09 11:44 ` Benjamin Herrenschmidt
2016-12-09 12:33 ` Geert Uytterhoeven
2016-12-09 12:33 ` Geert Uytterhoeven
2016-12-09 12:33 ` Geert Uytterhoeven
2016-12-09 13:19 ` Lucas Stach
2016-12-09 13:19 ` Lucas Stach
2016-12-09 13:19 ` Lucas Stach
2016-12-09 13:33 ` Daniel Vetter
2016-12-09 13:33 ` Daniel Vetter
2016-12-09 13:33 ` Daniel Vetter
2016-12-09 13:57 ` David Herrmann
2016-12-09 13:57 ` David Herrmann
2016-12-09 13:57 ` David Herrmann
2016-12-09 14:04 ` Daniel Vetter
2016-12-09 14:04 ` Daniel Vetter
2016-12-09 14:04 ` Daniel Vetter
2016-12-09 20:29 ` Benjamin Herrenschmidt
2016-12-09 20:29 ` Benjamin Herrenschmidt
2016-12-09 20:29 ` Benjamin Herrenschmidt
2016-12-09 8:30 ` Daniel Vetter
2016-12-09 8:30 ` Daniel Vetter
2016-12-09 8:30 ` Daniel Vetter
2016-12-08 14:59 ` Jani Nikula
2016-12-08 14:59 ` Jani Nikula
2016-12-08 14:59 ` Jani Nikula
2016-12-08 14:22 ` Daniel Vetter
2016-12-08 14:22 ` Daniel Vetter
2016-12-08 14:22 ` Daniel Vetter
2016-12-08 21:28 ` Benjamin Herrenschmidt
2016-12-08 21:28 ` Benjamin Herrenschmidt
2016-12-08 21:28 ` Benjamin Herrenschmidt
2016-12-09 0:08 ` Dave Airlie
2016-12-09 0:08 ` Dave Airlie
2016-12-09 0:08 ` Dave Airlie
2016-12-09 8:04 ` Geert Uytterhoeven
2016-12-09 8:04 ` Geert Uytterhoeven
2016-12-09 11:40 ` Benjamin Herrenschmidt
2016-12-09 11:40 ` Benjamin Herrenschmidt
2016-12-09 11:40 ` Benjamin Herrenschmidt
2016-12-13 7:33 ` Gerd Hoffmann
2016-12-13 7:33 ` Gerd Hoffmann
2016-12-13 7:33 ` Gerd Hoffmann
2016-12-13 15:17 ` Laurent Pinchart
2016-12-13 15:17 ` Laurent Pinchart
2016-12-13 15:17 ` Laurent Pinchart
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=1481158879.26959.41.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=arnaud.patard@rtp-net.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--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=thomas.petazzoni@free-electrons.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.