From: benh@kernel.crashing.org
To: <linuxppc-dev@lists.linuxppc.org>, Lars Brinkhoff <lars@nocrew.org>
Subject: Re: USB audio
Date: Thu, 21 Feb 2002 17:03:04 +0100 [thread overview]
Message-ID: <20020221160304.28138@mailhost.mipsys.com> (raw)
In-Reply-To: <85ofii3lk9.fsf@junk.nocrew.org>
>
>I got an iSub today. It's recognized as an USB audio device when it's
>connected, and it basically works, but there are two problems:
>
>* Whenever I kill a process (with ^C, to be precise) writing audio
> data to the iSub, that process hangs. From then on, all processes
> opening the dsp or mixer devices also hang. If I don't kill the
> process, suspending and resuming works fine.
I think I know what's wrong, I yet have write a fix though.
>* The "aumix" program (version 2.7) doesn't seem to think there is a
> volume control.
Don't know about this one.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-02-21 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-21 15:24 USB audio Lars Brinkhoff
2002-02-21 16:03 ` benh [this message]
2002-02-21 22:32 ` Alban Fellows
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=20020221160304.28138@mailhost.mipsys.com \
--to=benh@kernel.crashing.org \
--cc=lars@nocrew.org \
--cc=linuxppc-dev@lists.linuxppc.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).