Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933407AbcKHRLN (ORCPT ); Tue, 8 Nov 2016 12:11:13 -0500 Received: from mail-wm0-f68.google.com ([74.125.82.68]:32801 "EHLO mail-wm0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933370AbcKHRLK (ORCPT ); Tue, 8 Nov 2016 12:11:10 -0500 Date: Tue, 8 Nov 2016 18:11:06 +0100 From: Daniel Vetter To: Peter Zijlstra Cc: Stephen Rothwell , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Intel Graphics , DRI , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Chris Wilson , Joonas Lahtinen , Rob Clark Subject: Re: [Intel-gfx] linux-next: manual merge of the tip tree with the drm-intel tree Message-ID: <20161108171106.ugkcetcv3auvx7cz@phenom.ffwll.local> Mail-Followup-To: Peter Zijlstra , Stephen Rothwell , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Intel Graphics , DRI , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Chris Wilson , Joonas Lahtinen , Rob Clark References: <20161108152541.096711bb@canb.auug.org.au> <20161108104403.mi3onjfn65etrrtu@phenom.ffwll.local> <20161108132448.GG3117@twins.programming.kicks-ass.net> <20161108160916.56nxpkiupw3u7rgy@phenom.ffwll.local> <20161108170415.GM3117@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161108170415.GM3117@twins.programming.kicks-ass.net> X-Operating-System: Linux phenom 4.6.0-1-amd64 User-Agent: NeoMutt/20161014 (1.7.1) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1124 Lines: 24 On Tue, Nov 08, 2016 at 06:04:15PM +0100, Peter Zijlstra wrote: > On Tue, Nov 08, 2016 at 05:09:16PM +0100, Daniel Vetter wrote: > > > Now, I know you're working on getting rid of this entirely for i915, but > > > what about that MSM driver? Will we continue to need it there, is > > > anybody actually maintaining that thing? > > > > Rob Clark is, and since he's a one-man gpu driver team with other > > responsibilities it might take even longer than for i915 :( > > Fair enough. For my information, how much a of copy/paste job from i915 > was that? Could he, in principle, copy/paste your changes to get rid of > this back into MSM without too much effort, or have things diverged > greatly since the initial copy/paste? Probably diverged too much already, and on top the big part is the command submission, and that's entirely driver/hw specific. But etnaviv is a plain gem driver which uses per-bo locking, and there's all the ttm drivers with similar designs, so there's plenty of templates. But it's not just copypasta for sure. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch