From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Stefan Ringel <stefan.ringel@arcor.de>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: tm6000 autio isoc blocks
Date: Sun, 06 Jun 2010 12:20:51 -0300 [thread overview]
Message-ID: <4C0BBCD3.8000101@redhat.com> (raw)
In-Reply-To: <4C09686E.5090601@arcor.de>
Em 04-06-2010 17:56, Stefan Ringel escreveu:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Mauro,
>
> I have check the windows usb log and if I have audio block it's say 0
> byte, but the data is complete 180 bytes until next block header. So I
> think it's good if that audio block (cmd=2) resize from 0 to 180
AFAIK, even if the data is empty, all blocks have 180 bytes of size.
Yet, maybe the block size simply doesn't apply for audio... Tests are
needed to double check what's the case here.
Cheers,
Mauro
prev parent reply other threads:[~2010-06-06 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 20:56 tm6000 autio isoc blocks Stefan Ringel
2010-06-06 15:20 ` Mauro Carvalho Chehab [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=4C0BBCD3.8000101@redhat.com \
--to=mchehab@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=stefan.ringel@arcor.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;
as well as URLs for NNTP newsgroup(s).