From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Date: Tue, 29 Sep 2015 08:23:23 +0000 Subject: Re: No more new fbdev drivers, please Message-Id: <1443515003.21557.12.camel@redhat.com> List-Id: References: <5603EC15.9090605@ti.com> <20150924144621.40e26f0a@free-electrons.com> <20150924152312.GV3383@phenom.ffwll.local> <1443425953.19666.6.camel@redhat.com> <20150928123627.GD3383@phenom.ffwll.local> In-Reply-To: <20150928123627.GD3383@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 , Teddy Wang , Greg Kroah-Hartman , Daniel Vetter , "linux-kernel@vger.kernel.org" , DRI Development , Tomi Valkeinen , Geert Uytterhoeven , Laurent Pinchart , Arnaud Patard , Dave Airlie , Sudip Mukherjee On Mo, 2015-09-28 at 14:36 +0200, Daniel Vetter wrote: > On Mon, Sep 28, 2015 at 09:39:13AM +0200, Gerd Hoffmann wrote: > > Hi, > > > > > As Daniel mentioned, the connector+encoder+crtc combination is one of > > > those simplifications that would make sense if more such drivers are > > > added. > > > > Another one is memory management. It's pretty complex because it can > > handle _way_ more than what simple drivers need, and the result is > > _alot_ of ttm boilerplate in the drivers. > > ttm is pretty impressive overkill for most simplistic drm drivers. If you > just need contiguous framebuffers for display then the cma helpers should > take care of pretty much all the boilerplate for you. They have ready-made > simple gem and dumb framebuffer mmap support, which is all a basic kms > driver needs. Does that work on !arm meanwhile? Last time I checked (when writing bochsdrm, around v3.14) the cma helpers didn't even build on x86 ... cheers, Gerd