From: David Miller <davem@davemloft.net>
To: airlied@linux.ie
Cc: benh@kernel.crashing.org, dri-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/5]: ATI/RADEON DRM bug fixes...
Date: Thu, 12 Feb 2009 02:15:22 -0800 (PST) [thread overview]
Message-ID: <20090212.021522.217840575.davem@davemloft.net> (raw)
David, this work is against your drm-next branch.
Here are a collection of bug fixes for the Radeon DRM support. Most
of them have to do with trying to access kernel virtual addresses
using DRM_READ32() and DRM_WRITE32().
With these patches at least the writeback test works on sparc64 and
the CP is able to process commands in the ring. I'm now diagnosing
some further problem that's preventing Xorg from functioning fully but
I should be able to diagnose that soon.
You'll probably love patch #4 in this series, and it probably explains
all kinds of weird problems people run into with DRM on radeon cards.
Please apply, thanks.
next reply other threads:[~2009-02-12 10:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 10:15 David Miller [this message]
2009-02-12 11:26 ` [PATCH 0/5]: ATI/RADEON DRM bug fixes Dave Airlie
2009-02-12 22:19 ` David Miller
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=20090212.021522.217840575.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=airlied@linux.ie \
--cc=benh@kernel.crashing.org \
--cc=dri-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.