From: Lee Revell <rlrevell@joe-job.com>
To: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: old radeon latency problem still unfixed?
Date: Sat, 25 Feb 2006 21:36:55 -0500 [thread overview]
Message-ID: <1140921415.24141.92.camel@mindpipe> (raw)
In-Reply-To: <1140921200.12674.29.camel@cmn3.stanford.edu>
On Sat, 2006-02-25 at 18:33 -0800, Fernando Lopez-Lezcano 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?
>
> You mean on the plain vanilla stable kernel tree? Users running what?
>
Presumably.
> I'm using 2.6.15-rt18 currently on radeon machines (9250 chipset) with
> no problems that I can see.
We don't want to require the -rt kernel to use JACK at modest latencies,
that's like killing a fly with a gun.
Lee
next prev parent reply other threads:[~2006-02-26 2:36 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 [this message]
2006-02-26 9:13 ` Arjan van de Ven
2006-02-26 19:35 ` Lee Revell
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=1140921415.24141.92.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nando@ccrma.Stanford.EDU \
/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.