From: Andreas Oberritter <obi@linuxtv.org>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: "Rémi Denis-Courmont" <remi@remlab.net>,
"Linux Media Mailing List" <linux-media@vger.kernel.org>,
"Michael Krufky" <mkrufky@kernellabs.com>,
"Steven Toth" <stoth@kernellabs.com>
Subject: Re: DVBv5 frontend library
Date: Thu, 10 Nov 2011 13:56:17 +0100 [thread overview]
Message-ID: <4EBBC9F1.4060103@linuxtv.org> (raw)
In-Reply-To: <4EBBBDF1.2050601@redhat.com>
On 10.11.2011 13:05, Mauro Carvalho Chehab wrote:
> Em 10-11-2011 05:08, Rémi Denis-Courmont escreveu:
>> For frequency, we also need a unit, since it depends on the
>> delivery system.
>
> The spec says:
> DTV_FREQUENCY
>
> Central frequency of the channel, in HZ.
>
> So, the unit should be Hz. If is there any place where something different is
> used, we should fix it to match what's specified there.
For DVB-S, the unit is and has always been kHz. The spec is wrong.
>> 5) Unless/Until the library implements scanning and some kind of channel
>> or transponder abstraction (e.g. unique ID per transponder), it is dubious
>> that it can really abstract new delivery systems. I mean, the tuning
>> parameters need to come from somewhere, so the application will have to
>> know about the delivery systems.
>
> Sure. This is the next item on my TODO list ;)
Make sure to generate globally unique IDs. Even though onid + tsid + sid
*should* identify a DVB service, in reality they don't. There are many
duplicates, especially with - but not limited to - reception of multiple
satellites.
Regards,
Andreas
prev parent reply other threads:[~2011-11-10 12:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 19:01 DVBv5 frontend library Mauro Carvalho Chehab
2011-11-10 7:08 ` Rémi Denis-Courmont
2011-11-10 12:05 ` Mauro Carvalho Chehab
2011-11-10 12:56 ` Andreas Oberritter [this message]
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=4EBBC9F1.4060103@linuxtv.org \
--to=obi@linuxtv.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=mkrufky@kernellabs.com \
--cc=remi@remlab.net \
--cc=stoth@kernellabs.com \
/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