From: Andreas Oberritter <obi@linuxtv.org>
To: "Thomas Schlöter" <thomas.schloeter@gmx.net>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] DVB Satellite Channel Routing support for DVB-S
Date: Mon, 10 Jan 2011 14:09:53 +0100 [thread overview]
Message-ID: <4D2B0521.1020404@linuxtv.org> (raw)
In-Reply-To: <BDD0B014-3AD5-4693-82D9-026F47A7F8A4@gmx.net>
Hallo Thomas,
thank you for your contribution. However, I'm against applying it.
On 01/10/2011 05:19 AM, Thomas Schlöter wrote:
> I have developed some modifications to the 2.6.37 DVB frontend code to support DVB satellite channel routing (aka "SCR", "Unicable", "EN50494"). Following this standard, all satellite tuners share the same cable and each of them has a fixed intermediate frequency it is supposed to tune to. Zapping is done by sending a special DiSEqC message while SEC voltage is temporarily pulled from 14 to 18 volts. This message includes the tuner's ID from 0 to 7, the frequency, band and polarisation to tune to as well as one out of two satellite positions.
>
> I decided this should be supported by the kernel frontend code as it is impossible to send that special DiSEqC / voltage sequence from userspace.
Why do you think that's impossible? There's a userspace implementation
in Enigma2.
> Additionally, it adds fully transparent support for SCR to arbitrary applications that use the DVB API, such as MythTV, VDR, xine etc.
That statement is not true, because you have to configure Unicable LNBs,
which you do using dvb-scr-setup.c.
Regards,
Andreas
next parent reply other threads:[~2011-01-10 13:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BDD0B014-3AD5-4693-82D9-026F47A7F8A4@gmx.net>
2011-01-10 13:09 ` Andreas Oberritter [this message]
2011-01-10 15:07 ` [PATCH] DVB Satellite Channel Routing support for DVB-S Thomas Schlöter
2011-01-10 15:54 ` Andreas Oberritter
2011-01-10 17:28 ` Oliver Endriss
2011-01-10 18:10 ` [InfraSchlot SPAM Check] " Thomas Schlöter
2011-01-10 18:01 ` Thomas Schlöter
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=4D2B0521.1020404@linuxtv.org \
--to=obi@linuxtv.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=thomas.schloeter@gmx.net \
/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