public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Josef Wolf <jw@raven.inka.de>
Cc: linux-media@vger.kernel.org
Subject: Re: SYS_DVBS vs. SYS_DVBS2
Date: Wed, 19 Dec 2018 09:22:11 -0200	[thread overview]
Message-ID: <20181219092211.16d67c61@coco.lan> (raw)
In-Reply-To: <20181219102846.GJ11337@raven.inka.de>

Em Wed, 19 Dec 2018 11:28:46 +0100
Josef Wolf <jw@raven.inka.de> escreveu:

> Hello experts,
> 
> hope I'm on the correct list for my question. Plese give me a pointer to the
> correct list if I'm off-topic here.
> 
> I would like to know how to know whether for a specific program SYS_DVBS or
> SYS_DVBS2 should be specified to the FE_SET_PROPERTY ioctl() call.

This is not specific to a program. It affects the hole transponder. Either
the transponder is DVB-S or DVB-S2.

> Is this somehow broadcasted in some PAT/PMT tables?

It is at the NAT tables. They contain all needed information to properly
tune into the transponders. There are different tables, depending if the
transponder is -S or -S2.

> Or is it possible to simple always specify SYS_DVBS2 and the kernel will
> manage the backwards compatibilities when a DVB-S transponder is specified in
> the tuning parameters?

The Kernel can't and shouldn't guess the tuning parameters. It depends
on userspace to parse the NAT tables and get it right.

If you use dvbv5-scan, for example, the logic at libdvbv5 will parse the
NAT tables for you and write the tuning parameters right for each
transponder, ensuring that every program inside that transponder will
receive the same tuning parameters.

Thanks,
Mauro

  reply	other threads:[~2018-12-19 11:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-19 10:28 SYS_DVBS vs. SYS_DVBS2 Josef Wolf
2018-12-19 11:22 ` Mauro Carvalho Chehab [this message]
2018-12-19 12:16   ` Josef Wolf
2018-12-19 14:11     ` Mauro Carvalho Chehab

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=20181219092211.16d67c61@coco.lan \
    --to=mchehab+samsung@kernel.org \
    --cc=jw@raven.inka.de \
    --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