From: Antti Palosaari <crope@iki.fi>
To: "Aleksandr V. Piskunov" <aleksandr.v.piskunov@gmail.com>
Cc: Markus Rechberger <mrechberger@gmail.com>,
Devin Heitmueller <dheitmueller@kernellabs.com>,
Clinton Meyer <clintonmeyer22@gmail.com>,
Linux Media <linux-media@vger.kernel.org>
Subject: Re: LinuxTV firmware blocks all wireless connections / traffic
Date: Fri, 11 Sep 2009 22:47:25 +0300 [thread overview]
Message-ID: <4AAAA94D.1040609@iki.fi> (raw)
In-Reply-To: <20090911175030.GA10479@moon>
On 09/11/2009 08:50 PM, Aleksandr V. Piskunov wrote:
> Ok, I did read basics of USB 2.0 protocol, gotta love these 600 page specs..
> So using my fresh knowledge I went away and hacked ce6230 to use Isochronous
> transfer endpoint instead of Bulk one. And it helped, tuner works, no
> corruption with af9015 running on same controller at the same time.
Looks like chipset driver issue as you said.
> Of course it isn't a fix per se, af9015 still corrupts if I start bulk
> reading from a flash drive, etc. And there are no Isochronous endpoints on
> af9015, so no alternative to bulk transfers :)
y, correct. Welcome to hacking DVB drivers.
> But at least I'm getting closer to pinpointing the real problem and so far
> everything points to AMD SB700 chipset driver. Google says it has quite
> some hardware bugs and several workarounds in linux drivers...
>
> P.S. Rather unrelated question, what type of USB transfer is generally
> preferred for USB media stream devices, BULK or ISOC? Antti, why did you
> choose BULK for ce6230?
Because chipset Windows driver was using BULK. Very many, I think even
most, DVB chipset offers both ISOC and BULK. BULK is still used
commonly, only few drivers are using ISOC. Devin answered already why
BULK is used generally for DVB streams. :)
I read also USB "bible" book yesterday and it says it is better to use
biggest BULK urb supported. I want to change it biggest possible one,
but there is other side that limits it - memory needed for buffers.
That's why I am thinking twice whether to increase it 8k or 16k or even
more. I currently think 16k will be good compromise for most
configurations / devices.
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2009-09-11 19:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 21:43 LinuxTV firmware blocks all wireless connections / traffic Clinton Meyer
2009-09-09 21:59 ` Devin Heitmueller
2009-09-10 9:14 ` Aleksandr V. Piskunov
2009-09-10 10:58 ` Markus Rechberger
2009-09-10 12:45 ` Aleksandr V. Piskunov
2009-09-10 12:48 ` Aleksandr V. Piskunov
2009-09-10 13:12 ` Antti Palosaari
2009-09-10 13:41 ` Aleksandr V. Piskunov
2009-09-10 13:47 ` Antti Palosaari
2009-09-10 14:48 ` Antti Palosaari
2009-09-10 15:26 ` Devin Heitmueller
2009-09-10 15:55 ` Antti Palosaari
2009-09-10 16:12 ` Devin Heitmueller
2009-09-10 16:48 ` Antti Palosaari
2009-09-10 17:17 ` Devin Heitmueller
2009-09-10 20:29 ` Antti Palosaari
2009-09-10 20:45 ` Devin Heitmueller
2009-09-10 17:16 ` Aleksandr V. Piskunov
2009-09-10 19:39 ` Aleksandr V. Piskunov
2009-09-11 14:38 ` Antti Palosaari
2009-09-11 17:50 ` Aleksandr V. Piskunov
2009-09-11 18:01 ` Devin Heitmueller
2009-09-11 19:47 ` Antti Palosaari [this message]
2009-09-12 15:46 ` CityK
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=4AAAA94D.1040609@iki.fi \
--to=crope@iki.fi \
--cc=aleksandr.v.piskunov@gmail.com \
--cc=clintonmeyer22@gmail.com \
--cc=dheitmueller@kernellabs.com \
--cc=linux-media@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