From: Nicholas Knight <tegeran@home.com>
To: linux-kernel@vger.kernel.org
Subject: via82cxxx_audio driver bug?
Date: Mon, 13 Aug 2001 07:19:42 -0700 [thread overview]
Message-ID: <01081307194201.00276@c779218-a> (raw)
(my apologies if this gets seen as a little offtopic, I felt this was the
best place to get results from people who knew what was going on with
drivers)
My writeup on the bug when I belived it was definitely an XMMS bug is
avalible here:
http://bugs.xmms.org/show_bug.cgi?id=115
you'll need to scroll down to see details on what I isolated it to
I just sent email to the maintainer of the via82cxxx_audio driver
regarding this bug, hopefully I'll hear back from him soon, but I'd also
like to hear from anyone else who has used and/or hacked at this driver,
and if they've seen XMMS or other audio applications with access to
/dev/mixer have strange, temporarily lockups when not in root/realtime
priority. I've yet to be able to test this with other audio applications
besides XMMS.
Thanks.
next reply other threads:[~2001-08-13 14:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-13 14:19 Nicholas Knight [this message]
2001-08-13 15:19 ` via82cxxx_audio driver bug? Adrian Cox
2001-08-14 4:09 ` Nicholas Knight
2001-08-14 6:47 ` Martin Hoeller
2001-08-14 8:25 ` Adrian Cox
2001-08-13 17:36 ` Anton Altaparmakov
2001-08-13 17:46 ` Paul Jakma
2001-08-14 4:12 ` Nicholas Knight
2001-08-14 11:06 ` Paul Jakma
2001-08-14 11:28 ` Nicholas Knight
2001-08-14 19:01 ` Petr Baudis
[not found] <fa.csmnkev.1i5mrbt@ifi.uio.no>
[not found] ` <fa.fu9gjtv.lli1j7@ifi.uio.no>
[not found] ` <3B793D00.4090501@nyc.rr.com>
2001-08-14 15:05 ` Adrian Cox
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=01081307194201.00276@c779218-a \
--to=tegeran@home.com \
--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.