From: Hans Petter Selasky <hps@bitfrost.no>
To: linux-media@vger.kernel.org, Juergen Lock <nox@jelal.kn-bremen.de>
Subject: TT-USB2.0 and high bitrate packet loss (DVB-C/T)
Date: Thu, 30 May 2013 10:00:19 +0200 [thread overview]
Message-ID: <51A70713.6030802@bitfrost.no> (raw)
Hi there,
I need to get in concat with someone that can handle, test and review a
patch for TT-USB2.0. I've found that for certain high-bitrate streams,
the TT-USB2.0 sends more ISOCHRONOUS MPEG data than is specified in the
wMaxPacketSize fields. I have a USB analyzer capture which shows this
clearly. This of course won't be received at the USB host and packet
drops appear inside the stream. The solution is to use another alternate
setting. The technotrend chip has many of these. I've now tested using
alternate setting 7 instead of 3.
Alternate setting 7 allows transferring a maximum of 3 * 1024 bytes.
Alternate setting 3 allows transferring a maximum of 1 * 940 bytes.
--HPS
next reply other threads:[~2013-05-30 8:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 8:00 Hans Petter Selasky [this message]
2013-06-02 12:19 ` TT-USB2.0 and high bitrate packet loss (DVB-C/T) Hans Petter Selasky
2013-06-02 21:02 ` Antti Palosaari
2013-06-05 1:34 ` Antti Palosaari
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=51A70713.6030802@bitfrost.no \
--to=hps@bitfrost.no \
--cc=linux-media@vger.kernel.org \
--cc=nox@jelal.kn-bremen.de \
/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