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 16:54:14 +0100 [thread overview]
Message-ID: <4D2B2BA6.7030009@linuxtv.org> (raw)
In-Reply-To: <C8296DFF-0E53-4AA2-A6ED-CA8B83D424F2@gmx.net>
On 01/10/2011 04:07 PM, Thomas Schlöter wrote:
>>> 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.
>
> I think the kernel implementation would be superior for two reasons:
> - There are some timing requirements regarding the 14/18V transitions and the DiSEqC message which could perform better directly from the frontend code,
Unless there's proof, I won't believe that. We're not talking about
nanoseconds, but milliseconds, and it's about setting registers of slow
I2C devices. The same timing requirements are valid for each and every
backwards compatible DiSEqC sequence, which is the most common setting.
> - In many TV recording applications there is no support for SCR and it would be harder to implement in these. For VDR, there is a patch which is difficult to configure and has some technical limitations. In MythTV and XMBC I could not find any support for SCR. Their Wiki pages or forums say, that there are no plans for Unicable support as it would take huge changes.
Many of these applications didn't or don't support DiSEqC 1.1
(uncommittted switches) or DiSEqC 1.2 (rotor commands) or USALS. Still,
we don't put this logic into the kernel to make their life easier. Don't
add unneeded complexity to the kernel.
Of course, one could decide to start a reusable library to take care of
that stuff. Honestly, I don't know whether such a library exists today.
If you find the patch was simple enough to be applied to the kernel, it
must be as simple to patch your favourite application, even in a
platform independent way (not taking into account the required changes
to the UI, which have to be done anyway).
Regards,
Andreas
next prev parent reply other threads:[~2011-01-10 15:54 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 ` [PATCH] DVB Satellite Channel Routing support for DVB-S Andreas Oberritter
2011-01-10 15:07 ` Thomas Schlöter
2011-01-10 15:54 ` Andreas Oberritter [this message]
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=4D2B2BA6.7030009@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