From: Doychin Dokov <root@net1.cc>
To: unlisted-recipients:; (no To-header on input)@casper.infradead.org
Cc: linux-media@vger.kernel.org,
Konstantin Dimitrov <kosio.dimitrov@gmail.com>
Subject: Re: [PATCH] Add support for PCTV452E.
Date: Mon, 13 Jun 2011 01:34:02 +0300 [thread overview]
Message-ID: <4DF53EDA.5000207@net1.cc> (raw)
In-Reply-To: <4DF531BE.8090005@net1.cc>
I also confirmed it works with s2-liplianin on Debian's 2.6.38-bpo2
kernel without such problems.
Another thing I've tested is to compile the media_tree with the stb6100,
but the problem persist, so it seems it's not related to the component
that both devices share.
Any ideas what might be the reason for that, or at least where I should
focus at searching?
На 13.6.2011 г. 00:38 ч., Doychin Dokov написа:
> On 2.6.32.5 with s2-liplianin tree this is not observed, i.e. everything
> works as expected - the S2-3650 does not cause the TBS device to stutter.
>
> На 12.6.2011 г. 23:27 ч., Doychin Dokov написа:
>> The same thing happens when the devices are on different USB buses:
>> Bus 002 Device 004: ID 0b48:300a TechnoTrend AG TT-connect S2-3650 CI
>> Bus 001 Device 007: ID 0b48:3006 TechnoTrend AG TT-connect S-2400 DVB-S
>> Bus 001 Device 004: ID 734c:5980 TBS Technologies China
>>
>> When the S2-3650 CI scans, the stream output from the TBS is gone. When
>> it's done scanning / locking, the TBS continues to work fine. The S-2400
>> is not affected in any way, nor it affects the other receivers.
>>
>> It seems the issue is not relative to the devices being on the same USB
>> bus, nor the kernel used. I've tried Debian's 2.6.32.5 and 2.6.38-bpo2
>> on a Debian Squeeze system.
>>
>> На 11.6.2011 г. 19:38 ч., Doychin Dokov написа:
>>> i've been using the patches in the latest media_tree for some hours -
>>> the S2-3650 CI seems to work. There's one thing that disturbs me, though
>>> - when it scans / locks on a frequency, another device on the same PC,
>>> using the same stb6100, gets stuck for a moment. Any ideas what might be
>>> the cause for that? The two devices do not share common RF input signal,
>>> but are on the same USB bus:
>>> Bus 001 Device 004: ID 734c:5980 TBS Technologies China
>>> Bus 001 Device 003: ID 0b48:300a TechnoTrend AG TT-connect S2-3650 CI
>>>
>>> The TBS device is a QBOX2 SI, which works with their official driver
>>> from their web-site.
>>>
>>> There's also a third DVB device in the system - a TT S-2400 (which is on
>>> the other USB bus, though), which does not exhibit any problems related
>>> with the first two devices, nor causes them to get stuck when it's
>>> scanning.
>>>
>>> I'll try to switch devices around and see if anything changes.
>>>
>>
>
next prev parent reply other threads:[~2011-06-12 22:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201105242151.22826.hselasky@c2i.net>
2011-06-01 20:16 ` [PATCH] Add support for PCTV452E Mauro Carvalho Chehab
[not found] ` <4DF399EA.6090508@net1.cc>
[not found] ` <4DF52148.4060704@net1.cc>
[not found] ` <4DF531BE.8090005@net1.cc>
2011-06-12 22:34 ` Doychin Dokov [this message]
2011-06-15 15:44 ` Igor M. Liplianin
2011-09-13 6:04 ` Steffen Barszus
2011-09-27 7:55 ` Dominik Kuhlen
2011-09-27 11:28 ` Igor M. Liplianin
2011-09-27 11:36 ` Mauro Carvalho Chehab
2011-09-27 20:24 ` Dominik Kuhlen
2011-07-23 11:24 ` Steffen Barszus
2011-07-30 21:12 ` Oliver Freyermuth
2011-09-05 21:27 ` Oliver Freyermuth
2011-09-23 20:03 ` Mauro Carvalho Chehab
2011-09-23 20:22 ` Steffen Barszus
2011-09-23 20:26 ` Steffen Barszus
2011-09-23 20:48 ` Igor M. Liplianin
2011-09-23 20:58 ` Oliver Freyermuth
2011-09-23 21:11 ` Igor M. Liplianin
2011-09-23 21:38 ` Igor M. Liplianin
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=4DF53EDA.5000207@net1.cc \
--to=root@net1.cc \
--cc=kosio.dimitrov@gmail.com \
--cc=linux-media@vger.kernel.org \
/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