[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1481315374.17253.17.camel@kernel.crashing.org>
Date: Sat, 10 Dec 2016 07:29:34 +1100
From: Benjamin Herrenschmidt <benh@...nel.crashing.org>
To: David Herrmann <dh.herrmann@...il.com>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
Tomi Valkeinen <tomi.valkeinen@...com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Noralf Trønnes <noralf@...nnes.org>,
Sudip Mukherjee <sudipm.mukherjee@...il.com>,
Teddy Wang <teddy.wang@...iconmotion.com>,
Arnaud Patard <arnaud.patard@...-net.org>,
DRI Development <dri-devel@...ts.freedesktop.org>,
Linux Fbdev development list <linux-fbdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH 0/3] staging: remove fbdev drivers
On Fri, 2016-12-09 at 14:57 +0100, David Herrmann wrote:
> Despite all of this I still see no reason why a driver could not
> expose the static, real frambuffers via private ioctls. You can get
> all your fancy acceleration that way. Then fix user-space to use this
> API. If enough drivers end up with something similar, move it into the
> core. Just like we always do in DRM.
I don't care so much about userspace in my specific use case, more
about fbcon, which I think can be solved without too many hoops.
As for FB objects, my thinking is we could just use
unmap_mapping_ranges() to effectively change the mapping under the hood
of the app so it alternatively maps a bit of fb or a bit of memory...
Cheers,
Ben.
Powered by blists - more mailing lists