dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: alexdeucher@gmail.com
To: airlied@gmail.com, dri-devel@lists.freedesktop.org
Cc: Alex Deucher <alexander.deucher@amd.com>
Subject: [pull] radeon drm-fixes-3.8
Date: Thu, 31 Jan 2013 18:23:53 -0500	[thread overview]
Message-ID: <1359674633-4026-1-git-send-email-alexdeucher@gmail.com> (raw)

From: Alex Deucher <alexander.deucher@amd.com>

Hi Dave,

A few more radeon fixes for 3.8.  Mostly small stuff.  The big
change is disabling the use of the DMA ring for VM PT updates.  This
reverts back to the 3.7 behavior.  Problem is we can get huge PT
updates in certain cases that are too big for the DMA ring.  I've
got patches to use an IB for this so I can re-enable the use of the
DMA ring for VM PT updates in 3.9.  This request also includes the
patches from the last pull request I sent on Monday in case you haven't
pulled them yet.

The following changes since commit 483674325f64a37c7696edb12ce6ad3e535421bc:

  Merge branch 'drm-intel-fixes' of git://people.freedesktop.org/~danvet/drm-intel (2013-01-26 18:17:39 +1000)

are available in the git repository at:

  git://people.freedesktop.org/~agd5f/linux drm-fixes-3.8

Alex Deucher (7):
      drm/radeon: add WAIT_UNTIL to the non-VM safe regs list for cayman/TN
      drm/radeon: add quirk for RV100 board
      drm/radeon: fix backend map setup on 1 RB sumo boards
      drm/radeon/evergreen+: wait for the MC to settle after MC blackout
      drm/radeon/r5xx-r7xx: wait for the MC to settle after MC blackout
      drm/radeon: prevent crash in the ring space allocation
      drm/radeon: switch back to the CP ring for VM PT updates

Christopher Staite (1):
      drm/radeon: fix MC blackout on evergreen+

Mikko Tiihonen (1):
      drm/radeon: protect against div by 0 in backend setup

liu chuansheng (1):
      drm/radeon: Calling object_unrefer() when creating fb failure

 drivers/gpu/drm/radeon/evergreen.c      |   27 ++++++++++++++++++++++++---
 drivers/gpu/drm/radeon/r600.c           |    7 +++++--
 drivers/gpu/drm/radeon/radeon_asic.c    |    6 +++---
 drivers/gpu/drm/radeon/radeon_combios.c |    8 ++++++++
 drivers/gpu/drm/radeon/radeon_display.c |    4 +++-
 drivers/gpu/drm/radeon/radeon_ring.c    |    3 +++
 drivers/gpu/drm/radeon/reg_srcs/cayman  |    1 +
 drivers/gpu/drm/radeon/rv515.c          |    2 ++
 8 files changed, 49 insertions(+), 9 deletions(-)

             reply	other threads:[~2013-01-31 23:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31 23:23 alexdeucher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-01-28  3:46 [pull] radeon drm-fixes-3.8 alexdeucher
2013-01-25  2:53 alexdeucher
2013-01-15 14:21 alexdeucher
2013-01-17 18:30 ` Alex Deucher
2013-01-17 19:22   ` Marek Olšák
2013-01-10 22:42 alexdeucher
2013-01-07 17:11 alexdeucher
2013-01-04  2:46 alexdeucher
2012-12-20 23:39 alexdeucher
2012-12-21 16:14 ` Alex Deucher

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=1359674633-4026-1-git-send-email-alexdeucher@gmail.com \
    --to=alexdeucher@gmail.com \
    --cc=airlied@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=dri-devel@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;
as well as URLs for NNTP newsgroup(s).