From: alexdeucher@gmail.com
To: airlied@gmail.com, dri-devel@lists.freedesktop.org
Cc: Alex Deucher <alexander.deucher@amd.com>
Subject: [pull] radeon drm-next-3.8
Date: Wed, 12 Dec 2012 17:44:38 -0500 [thread overview]
Message-ID: <1355352278-1604-1-git-send-email-alexdeucher@gmail.com> (raw)
In-Reply-To: <1355179498-2018-1-git-send-email-alexdeucher@gmail.com>
From: Alex Deucher <alexander.deucher@amd.com>
Hi Dave,
One more pull for 3.8. This one adds CP DMA support and
several bug fixes.
Alex
The following changes since commit a636a9829175987e74ddd28a2e87ed17ff7adfdc:
Merge branch 'drm-next-3.8' of git://people.freedesktop.org/~agd5f/linux into drm-next (2012-12-11 08:46:03 +1000)
are available in the git repository at:
git://people.freedesktop.org/~agd5f/linux drm-next-3.8
Alex Deucher (6):
drm/radeon: improve mc_stop/mc_resume on r5xx-r7xx
drm/radeon: add register headers for CP DMA on r6xx-SI
drm/radeon: add support for CP DMA packet to r6xx/r7xx CS checker
drm/radeon: add support for CP DMA packet to evergreen CS checker
drm/radeon/cayman: add VM CS checker support for CP DMA
drm/radeon/si: add VM CS checker support for CP DMA
Jerome Glisse (3):
drm/radeon: do not move bo to different placement at each cs
drm/radeon: fix amd afusion gpu setup aka sumo v2
drm/radeon: fix fence driver for dma ring when wb is disabled
drivers/gpu/drm/radeon/evergreen.c | 8 +-
drivers/gpu/drm/radeon/evergreen_cs.c | 136 ++++++++++++++++++++++++++++++++
drivers/gpu/drm/radeon/evergreend.h | 49 ++++++++++++
drivers/gpu/drm/radeon/r600.c | 3 +-
drivers/gpu/drm/radeon/r600_cs.c | 72 +++++++++++++++++
drivers/gpu/drm/radeon/r600_reg.h | 9 ++
drivers/gpu/drm/radeon/r600d.h | 32 ++++++++
drivers/gpu/drm/radeon/radeon.h | 1 +
drivers/gpu/drm/radeon/radeon_asic.h | 1 +
drivers/gpu/drm/radeon/radeon_fence.c | 2 +-
drivers/gpu/drm/radeon/radeon_object.c | 18 ++---
drivers/gpu/drm/radeon/rv515.c | 122 +++++++++++++++++++++++++----
drivers/gpu/drm/radeon/si.c | 47 +++++++++++
drivers/gpu/drm/radeon/sid.h | 48 +++++++++++
14 files changed, 516 insertions(+), 32 deletions(-)
next prev parent reply other threads:[~2012-12-12 22:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-08 1:07 [pull] radeon drm-next-3.8 alexdeucher
2012-12-10 22:44 ` [pull] radeon drm-next-3.8 (v2) alexdeucher
2012-12-12 22:44 ` alexdeucher [this message]
2012-12-23 16:03 ` [pull] radeon drm-next-3.8 Rafał Miłecki
-- strict thread matches above, loose matches on Subject: below --
2012-12-15 0:06 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=1355352278-1604-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