From: Lee Revell <rlrevell@joe-job.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Thomas Hellström" <unichrome@shipmail.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Dave Airlie" <airlied@gmail.com>,
"dri-devel@lists.sourceforge.net"
<dri-devel@lists.sourceforge.net>
Subject: Re: 2.6.14-rt4: via DRM errors
Date: Fri, 25 Nov 2005 14:21:55 -0500 [thread overview]
Message-ID: <1132946515.20390.48.camel@mindpipe> (raw)
In-Reply-To: <1132935863.3298.36.camel@localhost.localdomain>
On Fri, 2005-11-25 at 16:24 +0000, Alan Cox wrote:
> On Iau, 2005-11-24 at 05:49 -0500, Lee Revell wrote:
> > what kind of lock it is or what it's protecting
> It co-ordinates access between the X server and various 3D clients so
> that they don't step on each others drawing. A shared memory area is
> used to co-ordinate other things like clip lists and what context may
> have been stomped by another user if when you retake the lock you were
> not last holder.
>
> Precisely what it protects is board dependant
OK. So it's schedulable.
Any debugging advice for a DRI driver (radeon not via) that I suspect is
causing scheduling blips and audio dropouts due to bus greediness or
other rude behavior? There seem to be a bunch of timeouts where it will
bit bang the hardware in a loop, should I try reducing these?
Lee
prev parent reply other threads:[~2005-11-25 19:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-24 4:53 2.6.14-rt4: via DRM errors Lee Revell
2005-11-24 9:52 ` Thomas Hellström
2005-11-24 10:44 ` Dave Airlie
2005-11-24 10:49 ` Lee Revell
2005-11-24 12:50 ` Thomas Hellström
2005-11-24 15:31 ` Jesse Barnes
2005-11-24 16:04 ` Thomas Hellström
2005-11-25 19:05 ` Lee Revell
2005-11-25 19:13 ` Arjan van de Ven
2005-11-25 19:23 ` Lee Revell
2005-11-25 20:06 ` Alan Cox
2005-11-25 16:24 ` Alan Cox
2005-11-25 19:21 ` Lee Revell [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=1132946515.20390.48.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=airlied@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dri-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=unichrome@shipmail.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).