From: Darron Broad <darron@kewl.org>
To: Andy Walls <awalls@radix.net>
Cc: linux-media@vger.kernel.org, Darron Broad <darron@kewl.org>,
linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] How to use scan-s2?
Date: Tue, 27 Jan 2009 14:11:27 +0000 [thread overview]
Message-ID: <7377.1233065487@kewl.org> (raw)
In-Reply-To: <1233017978.3061.2.camel@palomino.walls.org>
In message <1233017978.3061.2.camel@palomino.walls.org>, Andy Walls wrote:
LO
>On Mon, 2009-01-26 at 22:31 +0200, Alex Betis wrote:
>>
>> On Mon, Jan 26, 2009 at 10:20 PM, Darron Broad <darron@kewl.org>
>> wrote:
>> 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 :)
>
>Aside from Darron's observation, doesn't the result field of any
>particular S2API property return with a non-0 value on failure?
>
>(Sorry, I missed the original thread on the S2API return values.)
The actual tuning occurs within a thread and not when issuing
the tuning IOCTL. The only means to determine whether tuning
worked or not is inspection of the frontend events generated
within that thread. So, if the params are wrong, the IOCTL
can fail, but that's not the problem Alex is experiencing
where the params are correctly formed yet not supported in
the driver.
I did look at a means to expose supported params a while ago
but it's ugly so I haven't gone forward with it.
Bye
--
// /
{:)==={ Darron Broad <darron@kewl.org>
\\ \
next prev parent reply other threads:[~2009-01-27 14:11 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
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 [this message]
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=7377.1233065487@kewl.org \
--to=darron@kewl.org \
--cc=awalls@radix.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox