From: Pablo Yaggi <pyaggi@alsurdelsur.com>
To: Clemens Ladisch <cladisch@fastmail.net>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: C-Media / usb device bug ?
Date: Tue, 19 Sep 2006 04:17:50 -0300 [thread overview]
Message-ID: <200609190417.50321.pyaggi@alsurdelsur.com> (raw)
In-Reply-To: <1158647803.13410.271265867@webmail.messagingengine.com>
On Tuesday 19 September 2006 03:36, Clemens Ladisch wrote:
> Pablo Yaggi wrote:
> > I'm working in a multi-capture application with alsa and i discovered
> > if i attach two "c-media usb headphone set" adapters to an usb hub which
> > is attached to my computer when i try to read from the two devices the
> > first one read (also open) errors with (-77) bad file descriptor status
> > and the other one keep working. When i attach the two devices directly to
> > the usb connectors (without hub) all works fine, the two devices can be
> > read at the same time.
>
> What kernel version are you using?
>
> The EHCI transaction translator code (which is responsible for moving
> audio data through an high speed hub) got a bugfix in 2.6.17, but still
> artificially limits the bandwidth. It will be rewritten in 2.6.18.
>
>
> HTH
> Clemens
>
I tested it on 2.6.15, 2.6.16 and 2.6.17,
so you think the problem is EHCI ? is there anyway to check it ?
is it yet in rewriting process ?
Thank's
Pablo
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
prev parent reply other threads:[~2006-09-19 7:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 22:21 C-Media / usb device bug ? Pablo Yaggi
2006-09-19 6:36 ` Clemens Ladisch
2006-09-19 7:17 ` Pablo Yaggi [this message]
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=200609190417.50321.pyaggi@alsurdelsur.com \
--to=pyaggi@alsurdelsur.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=cladisch@fastmail.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.