From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Wilson Subject: Re: [PATCH 00/23] intel gtt rework, part 1: initialization Date: Thu, 02 Sep 2010 12:20:26 +0100 Message-ID: <89kc63$hv2gnv@fmsmga002.fm.intel.com> References: <1283373010-1314-1-git-send-email-daniel.vetter@ffwll.ch> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by gabe.freedesktop.org (Postfix) with ESMTP id C3CE39E7CA for ; Thu, 2 Sep 2010 04:20:29 -0700 (PDT) In-Reply-To: <1283373010-1314-1-git-send-email-daniel.vetter@ffwll.ch> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: intel-gfx@lists.freedesktop.org Cc: Daniel Vetter List-Id: intel-gfx@lists.freedesktop.org On Wed, 1 Sep 2010 22:29:47 +0200, Daniel Vetter wrote: > Patch series continuously tested on my ilk, i945gm and i855gm while > developing. IMHO the part most likely to suffer a regression is the > g33/pineview gtt size detection code. Boots on my PineView boxes, though since we still have a g33 GTT regression that is not completely reassuring. Still compiling for a couple of other gen3/4 boxes. Unspaghettifying this code is a good thing. Even if we can't remove the old dri interfaces, disentangling those code paths should help prevent future breakages. One can only hope. -- Chris Wilson, Intel Open Source Technology Centre