From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: "L. Hanisch" <dvb@flensrocker.de>
Cc: Christian Brunner <chb@muc.de>,
linux-media@vger.kernel.org, thomas.schloeter@gmx.net
Subject: Re: [PATCH] dvb: satellite channel routing (unicable) support
Date: Tue, 24 Jan 2012 11:01:11 -0200 [thread overview]
Message-ID: <4F1EAB97.6060301@redhat.com> (raw)
In-Reply-To: <4E837ACF.60804@flensrocker.de>
Hi,
Em 28-09-2011 16:51, L. Hanisch escreveu:
> Hi,
>
> Am 28.09.2011 21:04, schrieb Christian Brunner:
>> This is an updated version of the unicable patch by Thomas Schloeter
>> for linux 3.1.
>>
>> The patch is an addition to the dvb_frontend code, that adds fully
>> transparent support for SCR to arbitrary applications that use the
>> DVB API.
>>
>> I know that this patch has been rejected, because unicable support
>> can be implemented in userspace, too. However I like it anyway,
>> because there is a lot of software without unicable support out
>> there. I'm just sending it, because I think it could be usefull
>> for others.
>>
>> DVB satellite channel routing (aka "SCR", "Unicable", "EN50494") is
>> a standard, where all satellite tuners share the sam 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.
>>
>> By default SCR support is disabled and has to be enabled explicitly
>> via an ioctl command. At the same time you set the tuner's ID, the
>> frequency and other parameters. Thomas developed an utility
>> (dvb-scr-setup) to accomplish this task. It can be used unmodified.
>>
>> I'm using this patch successfully with a DUR-LINE UK 101 unicable LNB.
>
> That would be awesome to have this functionality in the kernel. I maintained the "unicable"-patch for the vdr (written by some guy from the vdr-portal.de who sadly doesn't seem to respond to mails via that forum anymore).
> It would be great if all the work could be summarized in one ioctl.
I don't think that SCR/Unicable, bandstacking, LNBf settings, rotor
control, etc. should belong to the Kernel. There are too many variants,
and several of them are not properly standardized or properly implemented.
Also, the actual options to use will depend on what type of DiSEqC components
used on his particular setup. So, it would be very difficult to write
something at the Kernel that will fit in all cases.
What the Kernel should support is the capability of sending/receiving DiSEqC
commands, allowing userspace libraries to do the job of setting it. Such
feature is already there, so there's no need to change anything there.
That's said, I'm working on a library to be used by applications that want
to talk with DVB devices. Together, with the library, there are a scanning
tool and a zapping tool.
So, inspired by this patch, and using a public tech note about SCR/Unicable [1],
I wrote an Unicable patch for such library:
http://git.linuxtv.org/v4l-utils.git/commit/6c2c00ed3722465ed781ad49567e34dc7a5f92e7
I'm currently without DVB-S/DVB-S2 antennas, so, I was not able to test it.
It would be very nice if you could help us by testing if those tools are
working with DVB-S with SCR, and, if not, help fixing its support.
[1] http://www.st.com/internet/com/TECHNICAL_RESOURCES/TECHNICAL_LITERATURE/APPLICATION_NOTE/CD00045084.pdf
Regards,
Mauro
next prev parent reply other threads:[~2012-01-24 13:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 19:04 [PATCH] dvb: satellite channel routing (unicable) support Christian Brunner
2011-09-28 19:51 ` L. Hanisch
2012-01-24 13:01 ` Mauro Carvalho Chehab [this message]
2012-01-24 18:30 ` Lars Hanisch
2012-01-24 18:47 ` 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=4F1EAB97.6060301@redhat.com \
--to=mchehab@redhat.com \
--cc=chb@muc.de \
--cc=dvb@flensrocker.de \
--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;
as well as URLs for NNTP newsgroup(s).