From: e9hack <e9hack@googlemail.com>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] [PATCH]Fix a bug in scan, which outputs the wrong frequency if the current tuned transponder is scanned only
Date: Mon, 08 Dec 2008 21:21:51 +0100 [thread overview]
Message-ID: <493D81DF.4010601@googlemail.com> (raw)
In-Reply-To: <c74595dc0812031328i32bc9997t632e0f63a8849b03@mail.gmail.com>
Alex Betis schrieb:
> There is no need for NIT message. I've added query from driver for currently
> tuned parameters - should work for DVB-T and DVB-C users. DVB-S/S2 will get
> IF frequency, which is not the real transponder frequency.
> Please update to latest version.
> Your other patch for DVB-C scan is also there.
>
> Let me know if it helps.
>
It works with the stv0297 and the tda10021 frontend. If the transponder was tuned with the
modulation QAM_AUTO, it would be better to read the current modulation from the frontend.
Currently, QAM_AUTO isn't implemented for a DVB-C frontend, but I'm working on an
implementation for the stv0297.
Regards,
Hartmut
_______________________________________________
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-12-08 20:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-17 12:51 [linux-dvb] [PATCH]Fix a bug in scan, which outputs the wrong frequency if the current tuned transponder is scanned only e9hack
2008-12-02 16:34 ` Christoph Pfister
2008-12-02 16:49 ` Alex Betis
2008-12-02 19:43 ` e9hack
2008-12-02 20:05 ` Alex Betis
2008-12-02 22:07 ` e9hack
2008-12-03 7:23 ` Alex Betis
2008-12-03 17:13 ` e9hack
2008-12-03 19:04 ` e9hack
2008-12-03 21:28 ` Alex Betis
2008-12-08 20:21 ` e9hack [this message]
2008-12-08 20:36 ` Alex Betis
2008-12-08 21:00 ` e9hack
2008-12-02 19:22 ` e9hack
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=493D81DF.4010601@googlemail.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 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.