From: Manu Abraham <abraham.manu@gmail.com>
To: Florian Lohoff <flo@rfc822.org>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] DVBFE_SET_PARAMS / delsys from fe_info ioctl ?
Date: Mon, 03 Mar 2008 18:17:58 +0400 [thread overview]
Message-ID: <47CC0896.3050308@gmail.com> (raw)
In-Reply-To: <20080303140316.GD12328@paradigm.rfc822.org>
Florian Lohoff wrote:
> On Mon, Mar 03, 2008 at 06:04:12PM +0400, Manu Abraham wrote:
>> The more important part is to first check for a signal, before
>> attempting a tune.
>> Lack of doing so, will result in a lot of frustration in many cases.
>> Though it is completely upto oneself whether to do it or not.
>
> You mean tune and then check if there is a SIGNAL and possibly a LOCK? I
> do that yes ... But first comes the tune - On an uninitialized state of
> a demod/tuner i would not expect to see any signal.
How do you expect to look for a signal level when using a rotor, for a
real life
example ?
Manu
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-03-03 14:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-01 16:14 [linux-dvb] DVBFE_SET_PARAMS / delsys from fe_info ioctl ? Florian Lohoff
2008-03-02 22:43 ` Manu Abraham
2008-03-02 23:36 ` Florian Lohoff
2008-03-03 0:22 ` Manu Abraham
2008-03-03 8:52 ` Florian Lohoff
2008-03-03 11:09 ` Manu Abraham
2008-03-03 11:26 ` Florian Lohoff
2008-03-03 12:03 ` Manu Abraham
2008-03-03 13:21 ` Florian Lohoff
2008-03-03 13:41 ` Manu Abraham
2008-03-03 13:44 ` Florian Lohoff
2008-03-03 13:55 ` Manu Abraham
2008-03-03 14:00 ` Florian Lohoff
2008-03-03 13:49 ` Manu Abraham
2008-03-03 13:48 ` Florian Lohoff
2008-03-03 14:04 ` Manu Abraham
2008-03-03 14:03 ` Florian Lohoff
2008-03-03 14:17 ` Manu Abraham [this message]
2008-03-03 14:13 ` Florian Lohoff
2008-03-03 14:24 ` Manu Abraham
2008-03-03 14:23 ` Florian Lohoff
2008-03-03 21:13 ` Christoph Pfister
2008-03-04 0:52 ` hermann pitton
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=47CC0896.3050308@gmail.com \
--to=abraham.manu@gmail.com \
--cc=flo@rfc822.org \
--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