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.7
Date: Wed, 24 Oct 2012 12:16:50 -0400	[thread overview]
Message-ID: <1351095410-1937-1-git-send-email-alexdeucher@gmail.com> (raw)

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

Hi Dave,

Fixes pull request for radeon.  The main things here are
fixing a ATPX regression from the acpi rework, fixing some
fallout from the async VM work, and fixing some module options
that were broken in certain cases.  Other than that, mainly
just bug fixes.

The following changes since commit b8e902f24fdd16c4373ddc37a4e150c4afe9c6db:

  drm/ttm: Fix a theoretical race in ttm_bo_cleanup_refs() (2012-10-23 10:15:21 +1000)

are available in the git repository at:
  git://people.freedesktop.org/~agd5f/linux drm-fixes-3.7

Alex Deucher (6):
      drm/radeon: add some new SI PCI ids
      drm/radeon: fix sparse warning
      drm/radeon: give each backlight a unique id
      drm/radeon: add error output if VM CS fails on cayman
      drm/radeon: fix ATPX function documentation
      drm/radeon: fix ATPX regression in acpi rework

Christian König (9):
      drm/radeon: fix PFP sync in vm_flush
      drm/radeon: fix cayman_vm_set_page v2
      drm/radeon: fix si_set_page v2
      drm/radeon: remove set_page check from VM code
      drm/radeon: fix header size estimation in VM code
      drm/radeon: fix and simplify pot argument checks v3
      drm/radeon: use vzalloc for gart pages
      drm/radeon: move size limits to gem_object_create.
      drm/radeon: move the retry to gem_object_create

 drivers/gpu/drm/radeon/atombios_encoders.c      |    5 ++-
 drivers/gpu/drm/radeon/evergreen_cs.c           |    1 +
 drivers/gpu/drm/radeon/ni.c                     |   45 ++++++++++-------
 drivers/gpu/drm/radeon/nid.h                    |    1 +
 drivers/gpu/drm/radeon/radeon_atpx_handler.c    |    6 +-
 drivers/gpu/drm/radeon/radeon_device.c          |   60 +++++++++--------------
 drivers/gpu/drm/radeon/radeon_gart.c            |   22 ++++-----
 drivers/gpu/drm/radeon/radeon_gem.c             |   18 ++++++-
 drivers/gpu/drm/radeon/radeon_legacy_encoders.c |    5 ++-
 drivers/gpu/drm/radeon/radeon_object.c          |   19 -------
 drivers/gpu/drm/radeon/si.c                     |   47 +++++++++++-------
 include/drm/drm_pciids.h                        |    3 +
 12 files changed, 122 insertions(+), 110 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2012-10-24 16:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-24 16:16 alexdeucher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-11-27 22:05 [pull] radeon drm-fixes-3.7 alexdeucher
2012-11-20 17:07 alexdeucher
2012-11-21 23:39 ` Alex Deucher
2012-11-15 14:23 alexdeucher
2012-11-07 14:40 alexdeucher
2012-11-08 15:28 ` Alex Deucher
2012-11-01 14:46 alexdeucher
2012-10-15 18:12 alexdeucher

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=1351095410-1937-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).