From: Clemens Ladisch <clemens@ladisch.de>
To: Kunal Singh <kunal@singhkunal.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: bandwidth issue with usb-audio in alsa
Date: Tue, 27 May 2008 17:34:05 +0200 [thread overview]
Message-ID: <483C29ED.6060504@ladisch.de> (raw)
In-Reply-To: <483C0847.1080405@singhkunal.com>
Kunal Singh wrote:
> I have some update on the issue which I had reported earlier. In my last e-mail, I had not mentioned that iPod is connected to the target through a USB (HS) Hub. When I connect the
> same hub to my Desktop and read its configuration using "usbview" - I see that "interval" for this hub is mentioned
> as "256 msec". (I have two hubs and I get all the results same with both the hubs).
Please show the output of "lsusb -v".
Regards,
Clemens
next prev parent reply other threads:[~2008-05-27 15:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 13:10 bandwidth issue with usb-audio in alsa Kunal Singh
2008-05-27 15:34 ` Clemens Ladisch [this message]
2008-05-27 15:47 ` Jon Smirl
-- strict thread matches above, loose matches on Subject: below --
2008-05-28 5:12 kunal
2008-05-28 3:03 kunal
2008-05-27 4:23 kunal
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=483C29ED.6060504@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=kunal@singhkunal.com \
/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