mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Anholt <eric@anholt.net>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] drm-intel pull request for 2.6.29-rc7
Date: Wed, 11 Mar 2009 11:29:35 -0700	[thread overview]
Message-ID: <1236796175.9354.28.camel@gaiman> (raw)

[-- Attachment #1: Type: text/plain, Size: 2083 bytes --]

You suggested at OSTS that I send pull requests to you directly, so here
goes.  Hopefully I'm doing it right (in particular, I'm not rebasing to
the very latest since you suggested you didn't want to see that having
happened just before the pull request, and I checked that nothing
conflicting has happened since the rebase).

There's a bunch of fencing fixes in here, which helps 915 and 945 3D
(especially 945 with my fix).  The fencing code could still use some
more love, but I know Chris Wilson's been exercising this fencing code
more than the actual released drivers do by a significant margin, and
the fixes do look good.  There's also the resume fix that we tested a
variant of at OSTS.

The following changes since commit 16b71fdf97599f1b1b7f38418ee9922d9f117396:
  Samuel CUELLA (1):
        i810: fix kernel crash fix when struct fb_var_screeninfo is supplied

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/anholt/drm-intel for-linus

Chris Wilson (4):
      drm/i915: First recheck for an empty fence register.
      drm/i915: Check fence status on every pin.
      drm/i915: Check to see if we've pinned all available fences
      drm/i915: Protect active fences on i915

Eric Anholt (2):
      drm/i915: Fix bad \n in MTRR failure notice.
      drm/i915: fix 945 fence register writes for fence 8 and above.

Kristian Høgsberg (1):
      drm: Return EINVAL on duplicate objects in execbuffer object list

Kyle McMartin (1):
      i915: add newline to i915_gem_object_pin failure msg

Pierre Willenbrock (1):
      drm/i915: Don't restore palettes through VGA registers.

 drivers/gpu/drm/i915/i915_dma.c     |    2 +-
 drivers/gpu/drm/i915/i915_drv.h     |    7 ++-
 drivers/gpu/drm/i915/i915_gem.c     |  115 +++++++++++++++++++++++++++-------
 drivers/gpu/drm/i915/i915_reg.h     |    1 +
 drivers/gpu/drm/i915/i915_suspend.c |   11 ---
 5 files changed, 99 insertions(+), 37 deletions(-)

-- 
Eric Anholt
eric@anholt.net                         eric.anholt@intel.com



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

                 reply	other threads:[~2009-03-11 18:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1236796175.9354.28.camel@gaiman \
    --to=eric@anholt.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®