public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Marco Lohse <mlohse@motama.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: linux-media@vger.kernel.org
Subject: Re: Problems with ngene based DVB cards (Digital Devices Cine S2 Dual 	DVB-S2 , Mystique SaTiX S2 Dual)
Date: Thu, 18 Mar 2010 16:07:06 +0100	[thread overview]
Message-ID: <4BA2419A.4070608@motama.com> (raw)
In-Reply-To: <829197381003180709t26f76b38y7e641b8c12a2d33d@mail.gmail.com>

Devin Heitmueller wrote:
> On Thu, Mar 18, 2010 at 6:00 AM, Andreas Besse <besse@motama.com> wrote:
>> Hello,
>>
>> We are now able to reproduce the problem faster and easier (using the
>> patched version of szap-s2 and the scripts included in the tar.gz :
>> http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/17334
>> and
>> http://cache.gmane.org//gmane/linux/drivers/video-input-infrastructure/17334-001.bin
>> )
> 
> This is pretty interesting.  I'm doing some ngene work over the next
> few weeks, so I will see if I can reproduce the behavior you are
> seeing here.
> 
> I noticed  that you are manually setting the "one_adapter=0" modprobe
> setting.  Does this have any bearing on the test results?
> 

I will try to answer this one:

No, leaving out this parameter does not change the test results; you
will only need to use different and additional parameters for szap-s2
for specifying the correct adapter and sub-devices.

By now, we also found out that the problems can be reproduced much easier:

0)

szap-s2 -H -c channels_DVB-S2_transponder_switch.conf -a 0 -n 1 -x |
grep Delay

Delay : 0.573021

1)

szap-s2 -H -c channels_DVB-S2_transponder_switch.conf -a 1 -n 1 -x |
grep Delay
Delay : 0.564667

2)

szap-s2 -H -c channels_DVB-S2_transponder_switch.conf -a 0 -n 1 -x |
grep Delay
Delay : 1.741931

Instead of 2) you can also run the included script

2')

./run_szap-s2_adapter0.sh

which will result in the device timeout after 30-40 iterations

To summarize

=> When opening and closing adapter0, then opening and closing devices
of adapter1, this will immediately result in problems.

And there a lot more variations of this bug, for example: actually read
data from adapter0, tune adapter1 using szap-s2, which will result in
adapter0 to be 'blocked' and not produce any more data after around 60 secs.

We are currently trying to dig into the source code of the driver to
solve the problems and would appreciate any help.

Have fun,
Marco

  reply	other threads:[~2010-03-18 15:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-17 16:41 Problems with ngene based DVB cards (Digital Devices Cine S2 Dual DVB-S2 , Mystique SaTiX S2 Dual) Andreas Besse
2010-03-18 10:00 ` Andreas Besse
2010-03-18 14:09   ` Devin Heitmueller
2010-03-18 15:07     ` Marco Lohse [this message]
2010-03-18 15:12       ` Devin Heitmueller
2010-03-23  9:35         ` Marco Lohse
2010-03-23  9:49           ` Marco Lohse
2010-03-24 17:18             ` Marco Lohse

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=4BA2419A.4070608@motama.com \
    --to=mlohse@motama.com \
    --cc=dheitmueller@kernellabs.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