public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: e9hack <e9hack@googlemail.com>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] [PATCH] Fix the unc for the frontends tda10021 and stv0297
Date: Sat, 31 May 2008 09:19:09 +0200	[thread overview]
Message-ID: <4840FBED.3050902@gmail.com> (raw)
In-Reply-To: <200805310146.30798@orion.escape-edv.de>

Oliver Endriss schrieb:
> Hi,
> 
> I just wanted to commit this changeset when I spotted this:
> 
> e9hack wrote:
>> @@ -266,6 +268,10 @@ static int tda10021_set_parameters (stru
>>  
>>         tda10021_setup_reg0 (state, reg0x00[qam], p->inversion);
>>  
>> +       /* reset uncorrected block counter */
>> +       state->last_lock = 0;
>> +       state->ucblocks = 0;
> 
> Note that UCB must count the number of uncorrected blocls during the
> lifetime of the driver. So it must not be reset during tuning.

I've add this reset for two reasons:

1) My second card uses a stv0297. The UCB value is always reset during the tuning, because 
the stv0297 is completely reinitialized. This occurs, if the frequency is changed or if 
the frontend lost the lock. I've add the reset to see the same behavior within the 
femon-plugin for both cards.

2) Above 650MHz, the signal strength of my cable is very low. It isn't usable. I get high 
BER and UCB values. The card with the tda10021 is a budget one. It is used for epg 
scanning in the background. It isn't possible to compare the UCB values of both cards, if 
the cards are tuned to the same frequency/channel and if the tda10021 was previous tuned 
to a frequency with a low signal.

-Hartmut

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

  parent reply	other threads:[~2008-05-31  7:19 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-10  8:46 [linux-dvb] [PATCH] Fix the unc for the frontends tda10021 and stv0297 e9hack
2008-05-10 15:17 ` Oliver Endriss
2008-05-10 15:27   ` Oliver Endriss
2008-05-10 15:48     ` Michael Krufky
2008-05-12 13:29       ` Oliver Endriss
2008-05-10 16:02     ` e9hack
2008-05-10 16:39       ` Oliver Endriss
2008-05-10 21:53     ` Andy Walls
2008-05-10 22:16       ` Manu Abraham
2008-05-10 23:44         ` Andy Walls
2008-05-11  6:14           ` Manu Abraham
2008-05-11 18:35             ` Andy Walls
2008-05-11 19:33               ` Manu Abraham
2008-05-11 21:32                 ` Andy Walls
2008-05-12 13:16                   ` Oliver Endriss
2008-05-12 13:47                     ` P. van Gaans
2008-05-12 16:02                       ` Oliver Endriss
2008-05-12 17:03                         ` P. van Gaans
2008-05-12 22:42                         ` Andy Walls
2008-05-11 23:45             ` P. van Gaans
2008-05-12  6:47               ` e9hack
2008-05-12 14:26               ` Luca Olivetti
2008-05-10 16:12   ` e9hack
2008-05-30 23:46 ` Oliver Endriss
2008-05-31  0:01   ` Manu Abraham
2008-05-31  7:19   ` e9hack [this message]
2008-05-31 12:45     ` Oliver Endriss

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=4840FBED.3050902@gmail.com \
    --to=e9hack@googlemail.com \
    --cc=linux-dvb@linuxtv.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