From mboxrd@z Thu Jan  1 00:00:00 1970
From: zaverel <zaverel@free.fr>
Subject: Re: Fwd: Re: bug in commit with Intel Core i3 3220T
 (Ivy Bridge hd graphics 2500)
Date: Thu, 28 Mar 2013 16:58:55 +0100
Message-ID: <515468BF.8030801@free.fr>
References: <51546298.2020900@free.fr> <51546333.3050003@free.fr>
	<20130328154525.GK4336@cantiga.alporthouse.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Content-Transfer-Encoding: quoted-printable
Return-path: <intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org>
Received: from smtp2-g21.free.fr (smtp2-g21.free.fr [212.27.42.2])
	by gabe.freedesktop.org (Postfix) with ESMTP id 062FAE6088
	for <intel-gfx@lists.freedesktop.org>;
	Thu, 28 Mar 2013 08:58:26 -0700 (PDT)
In-Reply-To: <20130328154525.GK4336@cantiga.alporthouse.com>
List-Unsubscribe: <http://lists.freedesktop.org/mailman/options/intel-gfx>,
	<mailto:intel-gfx-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/intel-gfx>
List-Post: <mailto:intel-gfx@lists.freedesktop.org>
List-Help: <mailto:intel-gfx-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/intel-gfx>,
	<mailto:intel-gfx-request@lists.freedesktop.org?subject=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: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
List-Id: intel-gfx@lists.freedesktop.org

Le 28/03/2013 16:45, Chris Wilson a =E9crit :
> On Thu, Mar 28, 2013 at 04:35:15PM +0100, zaverel wrote:
>> Hello,
>>
>> i attach
>>   i915_error_state
>> .zip
>>
>> intel_reg_read 0x20d0  =3D> 0x20D0 : 0x0
> Whoops, thanks very much for the report!
>
> commit 43181692f752f0a552d2e2c76d8379fe16e521cf
> Author: Chris Wilson <chris@chris-wilson.co.uk>
> Date:   Thu Mar 28 15:41:38 2013 +0000
>
>      sna/gen7: Refine is_gt2() for Haswell versus Ivybridge
>          =

>      The two similar chipsets do not use the same PCI-ID encoding
>      schema.
> -Chris
>

Just try your fix and that work.

Thanks

See you.