From: Lee Revell <rlrevell@joe-job.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: old radeon latency problem still unfixed?
Date: Sun, 26 Feb 2006 14:35:13 -0500 [thread overview]
Message-ID: <1140982513.24141.118.camel@mindpipe> (raw)
In-Reply-To: <1140945232.2934.0.camel@laptopd505.fenrus.org>
On Sun, 2006-02-26 at 10:13 +0100, Arjan van de Ven wrote:
> On Sat, 2006-02-25 at 20:36 -0500, Lee Revell wrote:
> > Users report that this patch:
> >
> > https://www.redhat.com/archives/fedora-devel-list/2004-June/msg00072.html
> >
> > is still needed to eliminate audio underruns for Radeon users.
> >
> > Any news on this?
>
> well that patch is not working (it's already in the mail, it schedules
> with spinlocks ;)
>
Understood, your response indicated that you would investigate a proper
solution.
> the other angle is that you're trading 3D performance vs audio
> performance....
>
AFAICT it's more like trading 3D performance for having audio work at
all. Other video drivers that were too aggressive and caused audio
dropouts (VIA) were fixed, even though there was a slight performance
cost.
Lee
next prev parent reply other threads:[~2006-02-26 19:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-26 1:36 old radeon latency problem still unfixed? Lee Revell
2006-02-26 2:33 ` Fernando Lopez-Lezcano
2006-02-26 2:36 ` Lee Revell
2006-02-26 9:13 ` Arjan van de Ven
2006-02-26 19:35 ` Lee Revell [this message]
2006-02-26 21:11 ` Benjamin Herrenschmidt
2006-02-26 21:31 ` Lee Revell
2006-02-26 22:53 ` Benjamin Herrenschmidt
2006-02-26 23:02 ` Lee Revell
2006-02-27 0:18 ` Benjamin Herrenschmidt
2006-02-27 0:32 ` Lee Revell
2006-02-26 9:44 ` Andrew Morton
2006-02-26 9:57 ` Arjan van de Ven
2006-02-26 19:39 ` Lee Revell
2006-02-26 21:31 ` Dave Airlie
2006-02-26 21:35 ` Lee Revell
2006-02-26 22:09 ` Dave Airlie
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=1140982513.24141.118.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=arjan@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox