public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Toth <stoth@linuxtv.org>
To: Aidan Thornton <makosoft@googlemail.com>
Cc: linux-dvb <linux-dvb@linuxtv.org>
Subject: Re: [linux-dvb] Hauppauge WinTV-CI Spec
Date: Thu, 27 Mar 2008 17:41:55 -0400	[thread overview]
Message-ID: <47EC14A3.7010505@linuxtv.org> (raw)
In-Reply-To: <c8b4dbe10803271428y13bd710co995e25bb9a2eb614@mail.gmail.com>

Aidan Thornton wrote:
> On Thu, Mar 27, 2008 at 7:57 PM, Steven Toth <stoth@linuxtv.org> wrote:
>> Aidan Thornton wrote:
>>  > On Thu, Mar 27, 2008 at 7:25 PM, Steven Toth <stoth@linuxtv.org> wrote:
>>  >> Recap: I said I'd notify the list when the spec was released for the
>>  >>  Hauppauge CI device.
>>  >>
>>  >>  Hello!
>>  >>
>>  >>  http://www.smardtv.com/index.php?page=dvbci&rubrique=specification
>>  >>
>>  >>  Looks like SmartDTV have finally got something out of the door. Put your
>>  >>  email address in their database and they'll email you the PDF with full
>>  >>  command interface describing the protocol.
>>  >>
>>  >>  Regards,
>>  >>
>>  >>  - Steve
>>  >
>>  > Hi,
>>  >
>>  > I'm not sure how that's relevant. It seems to be the spec for
>>  > something called CI+, intended to prevent unauthorised systems from
>>  > getting access to the decrypted stream coming out the CAM and ensure
>>  > only authorised host devices can use CAMs. I expect open source
>>  > software will be able to make use of this stuff approximately when
>>  > hell freezes over. If this catches on, say hello to more copy
>>  > protection and bye-bye to being able to use CAMs under Linux!
>>
>>  A subset of the spec will work with the CI USB device, for those that
>>  are interested.
> 
> Yeah, that's what I was wondering about - it doesn't seem to specify
> anything about CI USB devices, just the standard PC card based
> interface. (It even states that it doesn't deal with any interfaces
> other than that one). In what sense does the WinTV-CI implement this -
> does it translate between standard CIs and some subset of this
> protocol done over USB? (I'm not even sure, at a glance, if this makes
> sense.)

I only glanced at the spec, but from what I'm told the command API is 
implemented over USB. I suspect that Luc (the guy working on the Linux 
driver) might be able to consolidate this command set, with the USB logs 
he's been capturing. If not then something is clearly wrong.

I'd been promised this document during December 2007 by the vendor and 
said that I'd post it here to the community as soon as it was released.

- Steve



_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

  parent reply	other threads:[~2008-03-27 21:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-27 19:25 Hauppauge WinTV-CI Spec Steven Toth
2008-03-27 19:41 ` [linux-dvb] " Aidan Thornton
2008-03-27 19:57   ` Steven Toth
     [not found]     ` <c8b4dbe10803271428y13bd710co995e25bb9a2eb614@mail.gmail.com>
2008-03-27 21:41       ` Steven Toth [this message]
2008-04-08 13:24         ` Derk Dukker
2008-04-08 13:40           ` Steven Toth
2008-04-08 18:53             ` Luc Brosens

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=47EC14A3.7010505@linuxtv.org \
    --to=stoth@linuxtv.org \
    --cc=linux-dvb@linuxtv.org \
    --cc=makosoft@googlemail.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