[linux-dvb] Re: [PATCH] Twinhan/Twinhan-CA

[Manu Abraham <manu@kromtek.com>]

On Fri December 24 2004 2:54 pm, Andrew wrote:
> Manu Abraham >manu-nospam-at-kromtek.com< writes:
> >         Attached hereinwith is a set of patches for Twinhan based
> > cards.. for the impatient..
>
> This is fantastic that there is finaly some support for the CI part of the
> twinhan cards.
>
> I own a VP-1030A (red board) which I am trying your patch with. I applied
> the patch against CVS code from 23 Dec and it compiles cleanly and I can
> load the drivers without problems. When I run "dst_test info" all seems ok,
> I get
>
I have the very same board...

dst_test is used only to demonstrate the various ioctls and not for any 
practical use.. Maybe you ca use it to reset the CAM!

There is another application called ca_zap.
ca_zap requires the PMT_PID of the encrypted channel to function..
This PMT_PID is extracted from channels.conf.

scan does not yield a PMT_PID by default..
Therefore i have provided a patch to scan (option -h to provide the PMT_PID)
With this information you can find out the PMT_PID..

Once you have szap'd onto the encrypted channel,

You can do a ca_zap /path/to/channels.conf/having/PMT_PID "Channel name"
This will parse the CA_PMT and send it to the ASIC.

After this you can use mplayer to watch the encrypted stream.

Currently i am working on the PMT parser, so it may not be working for 
everybody, but it works for me.. But i hope to get it working very soon..

Manu

> Command = [info]
> APP: Number=[1]
> APP: Type=[1]
> APP: flags=[1]
> APP: CI High level interface
> APP: CA/CI Module Present
>
> And dmesg output:
>
> dst_ca_open: Device opened [cb45dd80]
> dst_ca_ioctl: Getting Slot info
> dst_put_ci:Write DST length=[8]:
> dst_put_ci: read successful
> dst_put_ci: ACK = [255]
> dst_put_ci: read successful
> dst_put_ci: Read Length = [4]
> dst_put_ci: read successful
> Success.
> ca_get_slot_info: Slot info = [213]
> ===================================
>  79 224 7 213 1 0 0 0
> Success.
> dst_ca_release: Device closed.
>
> When I run "dst_test pid" I run into problems, and the output
>
> Command = [pids]
> IOCTL failure
>
> And dmesg output:
> dst_ca_open: Device opened [d8530560]
> dst_ca_ioctl: Setting PID
> Failed.
> dst_ca_release: Device closed.
>
> Im running a 2.6.10 kernel, I might go down to 2.6.9 to see if this makes
> it any differn't.
>
> Even though it is not working for me its great to see cam support being
> added.
>
> Andrew.