public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Manu Abraham <abraham.manu@gmail.com>
To: Manu <eallaud@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: Re : [linux-dvb] Re : Technotrend Budget S2-3200 Digital artefacts on HDchannels
Date: Fri, 06 Feb 2009 03:50:18 +0400	[thread overview]
Message-ID: <498B7B3A.7050904@gmail.com> (raw)
In-Reply-To: <1233839327.6096.1@manu-laptop>

Manu wrote:
> Le 02.02.2009 18:43:33, Chris Silva a écrit :
>> On Tue, Jan 27, 2009 at 9:13 PM, Manu Abraham 
>> <abraham.manu@gmail.com>
>> wrote:
>>> Alex Betis wrote:
>>>> On Tue, Jan 27, 2009 at 9:56 PM, Manu Abraham
>> <abraham.manu@gmail.com>wrote:
>>>>>> Hmm OK, but is there by any chance a fix for those issues
>> somewhere or
>>>>>> in the pipe at least? I am willing to test (as I already
>> offered), I
>>>>>> can compile the drivers, spread printk or whatever else is 
>> needed
>> to
>>>>>> get useful reports. Let me know if I can help sort this problem.
>> BTW in
>>>>>> my case it is DVB-S2 30000 SR and FEC 5/6.
>>>>> It was quite not appreciable on my part to provide a fix or reply
>> in
>>>>> time nor spend much time on it earlier, but that said i was quite
>>>>> stuck up with some other things.
>>>>>
>>>>> Can you please pull a copy of the multiproto tree
>>>>> http://jusst.de/hg/multiproto or the v4l-dvb tree from
>>>>> http://jusst.de/hg/v4l-dvb
>>>>>
>>>>> and apply the following patch and comment what your result is ?
>>>>> Before applying please do check whether you still have the 
>> issues.
>>>> Manu,
>>>> I've tried to increase those timers long ago when played around
>> with my card
>>>> (Twinhan 1041) and scan utility.
>>>> I must say that I've concentrated mostly on DVB-S channels that
>> wasn't
>>>> always locking.
>>>> I didn't notice much improvements. The thing that did help was
>> increasing
>>>> the resolution of scan zigzags.
>>> With regards to the zig-zag, one bug is fixed in the v4l-dvb tree.
>>> Most likely you haven't tried that change.
>>>
>>>> I've sent a patch on that ML and people were happy with the
>> results.
>>> I did look at your patch, but that was completely against the 
>> tuning
>>> algorithm.
>>>
>>> [..]
>>>
>>>> I believe DVB-S2 lock suffer from the same problem, but in that
>> case the
>>>> zigzag is done in the chip and not in the driver.
>>> Along with the patch i sent, does the attached patch help you in
>>> anyway (This works out for DVB-S2 only)?
>>>
>> Manu,
>>
>> I've tried both multiproto branches you indicated above, *with* and
>> *without* the patches you sent to the ML (fix_iterations.patch and
>> increase timeout.patch) on this thread.
>> Sadly, same behavior as S2API V4L-DVB current branch. No lock on 
>> 30000
>> 3/4 channels. It achieves a 0.5 second jittery sound but no image. It
>> seems the driver is struggling to correctly lock on that channel, but
>> doesn't get there in time... Or maybe the hardware... Dunno...

Can you please send me a complete trace with the stb6100 and stb0899
modules loaded with verbose=5 for the 30MSPS transponder what you
are trying ? One simple szap would be enough (no scan please) based
on the http://jusst.de/hg/v4l-dvb tree.

Before you start testing, start clean from a cold boot after a
powerdown. This makes it a bit more easier identify things.

Regards,
Manu


  reply	other threads:[~2009-02-05 23:50 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-26 14:40 [linux-dvb] Technotrend Budget S2-3200 Digital artefacts on HDchannels Newsy Paper
2009-01-26 15:39 ` Chris Silva
2009-01-26 15:41   ` Chris Silva
2009-01-26 15:44     ` Alex Betis
2009-01-26 15:51       ` Chris Silva
2009-01-26 16:08         ` Chris Silva
2009-01-26 16:19           ` Alex Betis
2009-01-26 17:50             ` Manu Abraham
2009-01-26 18:18               ` Faruk A
2009-01-26 19:07               ` Alex Betis
2009-01-27 20:14                 ` Manu Abraham
2009-01-27 20:40                   ` Alex Betis
2009-01-27 21:27                     ` Manu Abraham
2009-01-27 21:45                       ` Manu Abraham
2009-01-27 22:02                       ` Alex Betis
2009-01-27 23:02                         ` Manu Abraham
2009-01-28 11:03                           ` n37
2009-01-28 16:19                             ` Re : " Manu
2009-01-28 17:07                               ` crow
2009-01-28 19:48                                 ` Manu Abraham
2009-01-28 18:04                               ` Goga777
2009-01-28 19:52                               ` Manu Abraham
2009-01-28 21:32                                 ` Re : " Manu
2009-01-28 22:43                                 ` Manu
2009-01-26 19:30               ` Manu
2009-01-26 20:12               ` Chris Silva
2009-01-26 20:28                 ` Ales Jurik
2009-01-27 20:05                   ` Manu Abraham
     [not found]               ` <1232998154.24736.2@manu-laptop>
2009-01-27 19:56                 ` [linux-dvb] Re : " Manu Abraham
2009-01-27 20:37                   ` Alex Betis
2009-01-27 21:13                     ` Manu Abraham
2009-01-27 21:31                       ` Alex Betis
2009-02-02 16:44                       ` Jonas Kvinge
2009-02-02 22:43                       ` Chris Silva
2009-02-02 23:46                         ` Re : " Manu
2009-02-05 13:08                         ` Manu
2009-02-05 23:50                           ` Manu Abraham [this message]
2009-02-06 15:22                             ` Re : " Manu
     [not found]                               ` <157f4a8c0902141355w3872bc0eif7796679f7f5323f@mail.gmail.com>
2009-02-14 22:34                                 ` Chris Silva
2009-02-14 22:46                                   ` Chris Silva

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=498B7B3A.7050904@gmail.com \
    --to=abraham.manu@gmail.com \
    --cc=eallaud@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