From: David Miller <davem@davemloft.net>
To: airlied@gmail.com
Cc: airlied@linux.ie, benh@kernel.crashing.org,
dri-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5]: ATI/RADEON DRM bug fixes...
Date: Thu, 12 Feb 2009 14:19:05 -0800 (PST) [thread overview]
Message-ID: <20090212.141905.48656767.davem@davemloft.net> (raw)
In-Reply-To: <21d7e9970902120326j2ce300d9x7df5a870c69a95f5@mail.gmail.com>
From: Dave Airlie <airlied@gmail.com>
Date: Thu, 12 Feb 2009 21:26:51 +1000
> On Thu, Feb 12, 2009 at 8:15 PM, David Miller <davem@davemloft.net> wrote:
> >
> > 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.
>
> Thanks Dave,
>
> These all look great, the EMITED one has potential to regress
> something by fixing it,
> but I think it might actually make things better, I'll push all of
> these to Linus asap as
> they all fix real bugs. I've put them into my drm-fixes branch and I'll try and
> re-review and get some testing tomorrow when I'm more awake.
Note that these depend upon Ben's drm_addmap and resource fixed in
your drm-next branch, sparc64 was also broken by those problems.
prev parent reply other threads:[~2009-02-12 22:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 10:15 [PATCH 0/5]: ATI/RADEON DRM bug fixes David Miller
2009-02-12 11:26 ` Dave Airlie
2009-02-12 22:19 ` David Miller [this message]
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.141905.48656767.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=airlied@gmail.com \
--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.