From: Clemens Ladisch <clemens@ladisch.de>
To: Markus Rechberger <mrechberger@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: snd_usb_audio
Date: Wed, 16 Nov 2005 10:11:09 +0100 [thread overview]
Message-ID: <1132132269.437af7ad5f8c4@www.domainfactory-webmail.de> (raw)
In-Reply-To: <d9def9db0511151518u10342e79r2a980683642051ff@mail.gmail.com>
Markus Rechberger wrote:
> finally the em28xx driver made it into the kerneltree, but one
> problem still remains
> the snd_usb_audio driver.
>
> The problem with the snd_usb_audio driver is that it only supports
> up to 10 isochronous packets.
This is packets per URB; we typically have 8 URBs.
> If people watch TV using such a framegrabber device and set audio
> to > 8000hz the video isoc transfer will break and the video will
> stop.
What exactly breaks? Are you using playback or capture?
If there is an underrun when starting a _playback_ stream, then it's a
known bug that has been fixed in 2.6.15-rc1.
> regarding usbaudio.c (in 2.6.14):
> #define MAX_PACKS 10
> #define MAX_PACKS_HS (MAX_PACKS * 8) /* in high speed mode */
>
> MAX_PACKS is the upper limit that is adjustable, the second one
> isn't used at all
>
> an easy hack would be to allow up to 100 packets but I also have a
> usb 1.1 soundblaster that might have problems with too many packets.
>
> The correct value for em28xx devices is around 80 packets.
Did you test this? Capturing doesn't use MAX_PACKS.
> does anyone know more about the packet limitations on USB 1.1 and
> 2.0 devices?
The only limitation are the host controller drivers.
HTH
Clemens
next prev parent reply other threads:[~2005-11-16 9:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 23:18 snd_usb_audio Markus Rechberger
2005-11-16 9:11 ` Clemens Ladisch [this message]
2005-11-16 11:07 ` snd_usb_audio Markus Rechberger
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=1132132269.437af7ad5f8c4@www.domainfactory-webmail.de \
--to=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mrechberger@gmail.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
all inboxes | Powered by JetHome®