From: Steffen Barszus <steffenbpunkt@googlemail.com>
To: Lutz Sammer <johns98@gmx.net>
Cc: linux-media@vger.kernel.org, liplianin@me.by, abraham.manu@gmail.com
Subject: Re: [PATCH] Fixes stb0899 not locking
Date: Thu, 21 Apr 2011 23:02:54 +0200 [thread overview]
Message-ID: <20110421230254.5b01c85e@grobi> (raw)
In-Reply-To: <4D99B357.50804@gmx.net>
On Mon, 04 Apr 2011 14:02:31 +0200
Lutz Sammer <johns98@gmx.net> wrote:
> Fixes stb0899 not locking.
> See http://www.spinics.net/lists/linux-media/msg30486.html ...
>
> When stb0899_check_data is entered, it could happen, that the data is
> already locked and the data search looped. stb0899_check_data fails
> to lock on a good frequency. stb0899_search_data uses an extrem big
> search step and fails to lock.
>
> The new code checks for lock before starting a new search.
> The first read ignores the loop bit, for the case that the loop bit is
> set during the search setup. I also added the msleep to reduce the
> traffic on the i2c bus.
Any updates on this one, or does this really need to be discussed. Its
proven now, that here is a bug, there was enough discussion before.
Can this PLEASE get applied.
What proofs are needed, anything wrong with it , at least ANY comment
on it ?
I'm starting to hate that its hidden trough v4l development causing that
DVB development is dead. This sucks ...
Is there any DVB developer on this list ? Someone who can check and
comment or approve this patch ?
Thanks !
next prev parent reply other threads:[~2011-04-21 21:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 12:02 [PATCH] Fixes stb0899 not locking Lutz Sammer
2011-04-18 5:48 ` Steffen Barszus
2011-04-21 21:02 ` Steffen Barszus [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-04-23 19:32 Issa Gorissen
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=20110421230254.5b01c85e@grobi \
--to=steffenbpunkt@googlemail.com \
--cc=abraham.manu@gmail.com \
--cc=johns98@gmx.net \
--cc=linux-media@vger.kernel.org \
--cc=liplianin@me.by \
/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