From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Date: Fri, 09 Dec 2016 11:44:16 +0000 Subject: Re: [RFC PATCH 0/3] staging: remove fbdev drivers Message-Id: <1481283856.27965.11.camel@kernel.crashing.org> List-Id: References: <1481158879.26959.41.camel@kernel.crashing.org> <20161208101005.6ufl3d4qvwprosju@phenom.ffwll.local> <20161208140210.rfyjf2265flsfpfj@phenom.ffwll.local> <20161208153735.74d7d350@free-electrons.com> <20161208152134.wnv4j4i6m5xpoycp@phenom.ffwll.local> <1481232877.26959.52.camel@kernel.crashing.org> <1481234249.26959.55.camel@kernel.crashing.org> <20161209083442.peoriqsto2llvl2t@phenom.ffwll.local> In-Reply-To: <20161209083442.peoriqsto2llvl2t@phenom.ffwll.local> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Daniel Vetter Cc: Thomas Petazzoni , Linux Fbdev development list , Teddy Wang , Greg Kroah-Hartman , "linux-kernel@vger.kernel.org" , DRI Development , Tomi Valkeinen , Geert Uytterhoeven , Sudip Mukherjee , Arnaud Patard On Fri, 2016-12-09 at 09:34 +0100, Daniel Vetter wrote: > Yeah if you have discrete vram then your dumb display driver isn't all > that pretty. We essentially just have the few drivers Dave hacked up to be > able to boot some servers. And there's definitely lots of room for more > shared code for those, and also some better infrastructure and helpers to > share more cod and make them better. > > The massive pile of dumb framebuffers we all merged over the past 2 years > all use system/dma memory for scanout, and for those we have the very nice > cma helpers that take care of everything for you. Do they work if the system/DMA memory has to be physically contiguous and at a fixed address ? The AST "ARM side" GPU is like that. > So it is possible, only reason vram dumb buffers look worse is that there's > only 3 and no one cares about them, vs about 20 and a very active community > of contributors (also for core drm improvements) for the other case. Well, we could move offb to drm while at it I suppose that would be another one (offb is the "dumb driver based on pre-programmed output by firmware). > Althought the MXSFB driver that just landed does use ttm and vram, so > maybe that's now improving too. Cheers, Ben.