From: "Tycho Lürsen" <tycholursen@gmail.com>
To: "Rudy Zijlstra" <rudy@grumpydevil.homelinux.org>,
"Honza Petrouš" <jpetrous@gmail.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: DVB Simulcrypt
Date: Mon, 23 Feb 2015 23:10:22 +0100 [thread overview]
Message-ID: <54EBA54E.9050002@gmail.com> (raw)
In-Reply-To: <54EB9B9F.5000400@grumpydevil.homelinux.org>
Op 23-02-15 om 22:29 schreef Rudy Zijlstra:
> On 23-02-15 20:56, Honza Petrouš wrote:
>> 2015-02-23 16:51 GMT+01:00 Rudy Zijlstra
>> <rudy@grumpydevil.homelinux.org>:
>>> And yes, my CAM's are for Irdeto and do not support Nagra. To my
>>> knowledge no valid Nagra CAM do exist for DVB-C
>> I'm a bit fossil regarding current status of CA in DVB but anyway I
>> can say
>> I know that some years ago existed CI-CAM modules for Nagra, it was
>> in time of so-called Nagra2 introduction on Hispasat ;)
>>
>> Dunno how is the current situation.
>>
>> An second - it has no difference if it is for sattelite or cable variant
>> of DVB. The CI-CAM standard is the same. The only problem
>> can be if support for particular provider is "baked" inside (meaning
>> only particular auth data are inserted).
>>
>>
> The point is that although from standard point of view you are right,
> no cable operator has ever wanted to support Nagra CAM. As a result
> the needed CAM authorization is not present.
>
> CI+ is a different story. Would need to check if CI+ is available in
> PC card form now. Kind of doubt that though. Do not expect Nagra wil
> support such development (refuse to validate).
>
> Cheers
>
>
> Rudy
Spare your time: no CI for PC is available that supports the bogus CI+
standard. And thus no driver for that too. So all you need is a simple
cardreader like the Smargo+ (but make sure you get an original one, not
a cheap clone that seemingly is the real deal)
Cheers,
Tycho
next prev parent reply other threads:[~2015-02-23 22:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-21 21:30 DVB Simulcrypt Rudy Zijlstra
2015-02-22 15:28 ` Rudy Zijlstra
[not found] ` <CAJbz7-2efvftG4=UAphyLFjjuFpLZQKCFDzqXrwb-mfDg4A7SQ@mail.gmail.com>
2015-02-23 10:34 ` Rudy Zijlstra
[not found] ` <54EB016D.8040105@grumpydevil.homelinux.org>
2015-02-23 11:21 ` Honza Petrouš
2015-02-23 12:44 ` Rudy Zijlstra
2015-02-23 14:21 ` Tycho Lürsen
2015-02-23 15:51 ` Rudy Zijlstra
2015-02-23 19:33 ` Tycho Lürsen
2015-02-23 19:56 ` Honza Petrouš
2015-02-23 20:32 ` Tycho Lürsen
2015-02-23 21:29 ` Rudy Zijlstra
2015-02-23 22:10 ` Tycho Lürsen [this message]
2015-02-23 14:53 ` Honza Petrouš
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=54EBA54E.9050002@gmail.com \
--to=tycholursen@gmail.com \
--cc=jpetrous@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=rudy@grumpydevil.homelinux.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