Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: zaverel <zaverel@free.fr>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
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	[thread overview]
Message-ID: <515468BF.8030801@free.fr> (raw)
In-Reply-To: <20130328154525.GK4336@cantiga.alporthouse.com>

Le 28/03/2013 16:45, Chris Wilson a écrit :
> On Thu, Mar 28, 2013 at 04:35:15PM +0100, zaverel wrote:
>> Hello,
>>
>> i attach
>>   i915_error_state
>> .zip
>>
>> intel_reg_read 0x20d0  => 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.

      reply	other threads:[~2013-03-28 15:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <51546298.2020900@free.fr>
2013-03-28 15:35 ` Fwd: Re: bug in commit with Intel Core i3 3220T (Ivy Bridge hd graphics 2500) zaverel
2013-03-28 15:45   ` Chris Wilson
2013-03-28 15:58     ` zaverel [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=515468BF.8030801@free.fr \
    --to=zaverel@free.fr \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox