From: Malcolm Priestley <tvboxspy@gmail.com>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
stakanov <stakanov@eclipso.eu>
Cc: Takashi Iwai <tiwai@suse.de>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: DVB-S PCI card regression on 4.19 / 4.20
Date: Wed, 21 Nov 2018 21:20:35 +0000 [thread overview]
Message-ID: <96849b97-3abb-b879-ed05-35bcd58b5e43@gmail.com> (raw)
In-Reply-To: <20181120140855.29f5dc3f@coco.lan>
On 20/11/2018 16:08, Mauro Carvalho Chehab wrote:
> Em Tue, 20 Nov 2018 14:20:01 +0100
<snip>
> Ok. Now, min/max frequencies are at the same scale. For DVB-S,
> dvb_frontend_get_frequency_limits() returns both in kHz, so the frequency
> range is now OK.
>
> The tuning frequency is wrong through. 10,719,000 kHz - e. g. 10,719 MHz
> seems to be the transponder frequency you're trying to tune, and not the
> intermediate frequency used at the DVB-S board.
>
> That sounds to me either a wrong LNBf setting or a bug at libdvbv5 or
> at Kaffeine's side. What happens is that the typical European LNBFs are:
>
> 1) the "old" universal one:
>
> UNIVERSAL
> Universal, Europe
> Freqs : 10800 to 11800 MHz, LO: 9750 MHz
> Freqs : 11600 to 12700 MHz, LO: 10600 MHz
I am pretty certain this type is obsolete it doesn't look right for 9750Mhz oscillator.
I am sure it was 10000Mhz or 96?? or something like that for old analogue transmissions of
20 years ago
>
> 2) the "new" universal one, with seems to be used by most modern
> satellite dishes in Europe nowadays:
>
> EXTENDED
> Astra 1E, European Universal Ku (extended)
This needs renaming as 1E has long gone.
Certainly this type is used for Astra 19.2 and 28.2.
Ideally we should use a default LNB type for each Satellite either in libdvbv5, Kaffeine or respective tables.
Regards
Malcolm
next prev parent reply other threads:[~2018-11-22 7:56 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4e0356d6303c128a3e6d0bcc453ba1be@mail.eclipso.de>
[not found] ` <20181120104217.5b487bcd@coco.lan>
[not found] ` <1593929.t9Y74Rdlh1@roadrunner.suse>
2018-11-20 16:08 ` DVB-S PCI card regression on 4.19 / 4.20 Mauro Carvalho Chehab
2018-11-21 21:20 ` Malcolm Priestley [this message]
2018-11-22 15:55 ` Mauro Carvalho Chehab
2018-11-22 16:19 ` Mauro Carvalho Chehab
2018-11-22 18:58 ` stakanov
2018-11-22 20:06 ` Mauro Carvalho Chehab
2018-11-22 20:19 ` stakanov
2018-11-22 20:35 ` Mauro Carvalho Chehab
2018-11-22 21:44 ` stakanov
2018-11-23 15:55 ` stakanov
2018-11-23 17:26 ` Mauro Carvalho Chehab
2018-11-26 13:31 ` Takashi Iwai
2018-11-27 10:02 ` stakanov
2018-11-27 12:49 ` Mauro Carvalho Chehab
2018-11-27 15:58 ` stakanov
2018-11-27 16:03 ` Takashi Iwai
2018-11-27 17:53 ` Mauro Carvalho Chehab
2018-11-27 18:09 ` Mauro Carvalho Chehab
2018-11-19 15:13 Takashi Iwai
2018-11-19 17:53 ` Mauro Carvalho Chehab
2018-11-19 19:07 ` Malcolm Priestley
2018-11-19 19:47 ` Takashi Iwai
2018-11-19 22:59 ` stakanov
2018-11-19 23:08 ` Mauro Carvalho Chehab
2018-11-19 23:19 ` stakanov
2018-11-19 23:58 ` Mauro Carvalho Chehab
2018-11-20 8:07 ` stakanov
2018-11-20 9:18 ` Mauro Carvalho Chehab
2018-11-20 9:51 ` stakanov
2018-11-20 9:54 ` Takashi Iwai
2018-11-20 10:26 ` Mauro Carvalho Chehab
2018-11-20 11:11 ` Takashi Iwai
2018-11-20 11:28 ` Mauro Carvalho Chehab
2018-11-20 7:12 ` Takashi Iwai
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=96849b97-3abb-b879-ed05-35bcd58b5e43@gmail.com \
--to=tvboxspy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=stakanov@eclipso.eu \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).