From: Lee Revell <rlrevell@joe-job.com>
To: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Remove xrun debugging?
Date: Sun, 23 Apr 2006 00:43:24 -0400 [thread overview]
Message-ID: <1145767405.21377.20.camel@mindpipe> (raw)
Can the xrun debug feature of ALSA please be removed? It was obsoleted
long ago by the latency tracing feature of the -rt kernel, and has not
been used to find a bug since 2004. At this point it's just confusing
to users.
Lee
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next reply other threads:[~2006-04-23 4:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-23 4:43 Lee Revell [this message]
2006-04-23 8:51 ` Remove xrun debugging? CE
2006-04-23 15:45 ` Florian Schmidt
2006-04-23 16:18 ` Lee Revell
2006-04-23 19:03 ` Florian Schmidt
2006-04-24 8:55 ` Jaroslav Kysela
2006-04-24 10:42 ` Martin Habets
2006-04-24 12:47 ` Takashi Iwai
2006-04-23 20:56 ` John Rigg
2006-04-23 20:53 ` Lee Revell
2006-04-24 12:50 ` Takashi Iwai
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=1145767405.21377.20.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
/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