Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Alexey Fisher <bug-track@fisher-privat.net>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [regression] agp/intel: Sandybridge doesnt require GMCH enabling
Date: Sun, 31 Oct 2010 10:31:45 +0000	[thread overview]
Message-ID: <5b55a1$ih5i18@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <1288520958.5299.4.camel@zwerg>

On Sun, 31 Oct 2010 11:29:18 +0100, Alexey Fisher <bug-track@fisher-privat.net> wrote:
> after commit e380f60b22eddec7825224b8d788572c82b63161
> intel driver filed to load, so system fallback to vesa driver.

*grin*

I'm looking right now at how many systems we were poking bits in
registers that were undefined.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

      reply	other threads:[~2010-10-31 10:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-31 10:29 [regression] agp/intel: Sandybridge doesn't require GMCH enabling Alexey Fisher
2010-10-31 10:31 ` Chris Wilson [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='5b55a1$ih5i18@fmsmga002.fm.intel.com' \
    --to=chris@chris-wilson.co.uk \
    --cc=bug-track@fisher-privat.net \
    --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