From: Darron Broad <darron@kewl.org>
To: Alex Betis <alex.betis@gmail.com>
Cc: Darron Broad <darron@kewl.org>,
linux-media@vger.kernel.org, linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] How to use scan-s2?
Date: Mon, 26 Jan 2009 20:20:31 +0000 [thread overview]
Message-ID: <18268.1233001231@kewl.org> (raw)
In-Reply-To: <c74595dc0901261130k6bdb6882lfb18c650cbca4abf@mail.gmail.com>
In message <c74595dc0901261130k6bdb6882lfb18c650cbca4abf@mail.gmail.com>, Alex
Betis wrote:
>
>On Mon, Jan 26, 2009 at 7:32 PM, Darron Broad <darron@kewl.org> wrote:
>
>> In message <c74595dc0901260753x8b9185fu33f2a96ffbe13016@mail.gmail.com>,
>> Alex Betis wrote:
>>
>> lo
>>
>> <snip>
>> >
>> >The bug is in S2API that doesn't return ANY error message at all :)
>> >So the tuner is left locked on previous channel.
>> >
>> >There are many things that can be done in driver to improve the situation,
>> >but I'll leave it to someone who has card with cx24116 chips.
>>
>> When tuning the event status should change to 0 and if
>> it stays that way the tuning operation failed.
>>
>> If you read the frontend status directly then you will
>> retrieve the state of the previous tuning operation
>> that suceeded.
>
>What do you call an event status and what direct status?
>
>scan-s2 uses FE_READ_STATUS that always success and indicates channel lock,
>even if cx24116 driver returned an error due to AUTO parameters.
refer to
FE_SET_FRONTEND:
http://www.linuxtv.org/docs/dvbapi/DVB_Frontend_API.html#SECTION00328000000000000000
and,
FE_GET_EVENT
http://www.linuxtv.org/docs/dvbapi/DVB_Frontend_API.html#SECTION003210000000000000000
l8r
--
// /
{:)==={ Darron Broad <darron@kewl.org>
\\ \
next prev parent reply other threads:[~2009-01-26 20:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-25 10:29 [linux-dvb] How to use scan-s2? Artem Makhutov
2009-01-25 9:49 ` Jens Krehbiel-Gräther
2009-01-25 13:25 ` Alex Betis
2009-01-25 14:41 ` Hans Werner
2009-01-25 14:54 ` Alex Betis
2009-01-25 16:29 ` Hans Werner
2009-01-25 16:56 ` Alex Betis
2009-01-26 3:24 ` BOUWSMA Barry
2009-01-25 23:48 ` Mika Laitio
2009-01-26 9:35 ` Alex Betis
2009-01-26 15:43 ` Mika Laitio
2009-01-26 15:53 ` Alex Betis
2009-01-26 17:32 ` Darron Broad
2009-01-26 19:30 ` Alex Betis
2009-01-26 20:20 ` Darron Broad [this message]
2009-01-26 20:31 ` Alex Betis
2009-01-27 0:59 ` Andy Walls
2009-01-27 7:48 ` Alex Betis
2009-01-27 14:11 ` Darron Broad
2009-01-27 14:07 ` Darron Broad
2009-01-26 19:44 ` Goga777
2009-01-25 14:25 ` Artem Makhutov
2009-01-25 17:48 ` Goga777
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=18268.1233001231@kewl.org \
--to=darron@kewl.org \
--cc=alex.betis@gmail.com \
--cc=linux-dvb@linuxtv.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.