From: Andrew Burgess <aab@cichlid.com>
To: alsa-devel@lists.sourceforge.net
Subject: Re: snd-usb-audio hacking
Date: Thu, 17 Jul 2003 08:18:03 -0700 [thread overview]
Message-ID: <200307171518.h6HFI3w11165@athlon.cichlid.com> (raw)
>Playback sort of works at this rate, using OSS emulation - it looks like
>the device down-samples to 48kHz. I occasionally get oopses under
...
>Is this the right place to be asking these questions, (or should I go
>off to the usb dev lists etc.?)..
My philosophy is to check the oops backtrace. If it dies in usb then
bug the usb guys to make it more robust so even if it is an alsa
bug, usb should print an error rather than oops. Vice versa if it
dies in alsa.
USB/ALSA bugs are tough because of two distinct developer camps.
I have a Griffin USB iMic that hard hangs 2.4.21ac just by running arecord and
then ^C. I got no response here a few weeks ago...
-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
next reply other threads:[~2003-07-17 15:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 15:18 Andrew Burgess [this message]
2003-07-17 18:21 ` Re: snd-usb-audio hacking Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2003-07-18 18:43 Andrew Burgess
2003-07-21 15:03 ` Takashi Iwai
[not found] <1_03071708263925499@cichlid.com>
2003-07-17 18:06 ` Andrew Burgess
2003-07-03 18:13 Tim Small
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=200307171518.h6HFI3w11165@athlon.cichlid.com \
--to=aab@cichlid.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 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.