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, 20 Dec 2012 18:39:39 -0500 [thread overview]
Message-ID: <1356046779-1579-1-git-send-email-alexdeucher@gmail.com> (raw)
From: Alex Deucher <alexander.deucher@amd.com>
Hi Dave,
Just a few fixes from the last week or so.
Alex
The following changes since commit 0953e76e91f4b6206cef50bd680696dc6bf1ef99:
drm/ttm: fix delayed ttm_bo_cleanup_refs_and_unlock delayed handling (2012-12-20 07:46:20 +1000)
are available in the git repository at:
git://people.freedesktop.org/~agd5f/linux drm-fixes-3.8
Jerome Glisse (4):
drm/radeon: don't leave fence blocked process on failed GPU reset
drm/radeon: avoid deadlock in pm path when waiting for fence
drm/radeon: restore modeset late in GPU reset path
drm/radeon: add support for MEM_WRITE packet
drivers/gpu/drm/radeon/evergreen_cs.c | 29 +++++++++++++++++++
drivers/gpu/drm/radeon/r600_cs.c | 29 +++++++++++++++++++
drivers/gpu/drm/radeon/radeon.h | 3 +-
drivers/gpu/drm/radeon/radeon_device.c | 17 +++++++++--
drivers/gpu/drm/radeon/radeon_drv.c | 3 +-
drivers/gpu/drm/radeon/radeon_fence.c | 49 +++++++++++++++++++++----------
drivers/gpu/drm/radeon/radeon_pm.c | 15 ++++++++--
7 files changed, 121 insertions(+), 24 deletions(-)
next reply other threads:[~2012-12-20 23:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 23:39 alexdeucher [this message]
2012-12-21 16:14 ` [pull] radeon drm-fixes-3.8 Alex Deucher
-- strict thread matches above, loose matches on Subject: below --
2013-01-04 2:46 alexdeucher
2013-01-07 17:11 alexdeucher
2013-01-10 22:42 alexdeucher
2013-01-15 14:21 alexdeucher
2013-01-17 18:30 ` Alex Deucher
2013-01-17 19:22 ` Marek Olšák
2013-01-25 2:53 alexdeucher
2013-01-28 3:46 alexdeucher
2013-01-31 23:23 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=1356046779-1579-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).