Mailing List archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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



On Sat December 18 2004 10:32 pm, Dominique Dumont wrote:
> Manu Abraham <manu@kromtek.com> writes:
> > You can try enabling the NXT6000, mt352, sp887x modules also in the
> > kernel config ... Don't disable those modules in  the config and try
> > again
> >
> > Should work fine ... with that way...
>
> Thanks. I've enabled all the frontends and now the kernel modules are
> correctly loaded:
>
> mt352                   5764  1 dvb_bt8xx
> sp887x                  8324  1 dvb_bt8xx
> dst_ca                 10636  1 dvb_bt8xx
> dst                    14792  2 dvb_bt8xx,dst_ca
> bt878                  11000  2 dvb_bt8xx,dst
> tuner                  20580  0
> bttv                  155788  2 dvb_bt8xx,bt878
> video_buf              22020  1 bttv
> firmware_class         10368  3 dvb_bt8xx,sp887x,bttv
> i2c_algo_bit            9928  1 bttv
> v4l2_common             6016  1 bttv
> btcx_risc               4616  1 bttv
> videodev                9920  1 bttv
> dvb_core               84520  2 dvb_bt8xx,dst_ca
> crc32                   4224  1 dvb_core
>
> Now, I'm going back to the fine doc to try dst_ca ...
>
> Stay tuned

Apply the patch to scan..
You will get an additional option to scan (-h)...

This will give you the PMT PID in channels.conf. Temporarily rename this 
channels.conf as for example, channels_pmt.conf or something else.

I have not made a patch for szap to accept PMT PID in it's config. Therefore 
temporarily you have to scan again without the (-h) option, to get the the 
standard channels.conf.

Use szap to szap to your channel... You should see the normal FE_LOCK, You 
could give the -r option also to szap.



Use the utility (i named this as ca_zap, this doesn't do any zapping but is a 
very simple PMT parser and converts to EN50221 format and sends the parsed 
data in EN50221 format to the driver.

The utility takes in 2 parameters, ie the channels.conf file with the PMT_PID 
and the channel name.


ie, for example 
ca_zap channels_pmt.conf "Channel name in channels_pmt.conf"
You will see the descriptors parsed and sent to the driver if you are in 
verbose/debug mode.


After this you can try out a simple test.

In the dvb-apps/test, you have 
test_dvr

It takes in parameters test_dvr output_file PID's.

You can just pipe the output to mplayer with a cache

for example...

 ./test_dvr /dev/stdout 282 516 654 | mplayer -cache 2048 - 
is what i did...

You should see your encrypted channel with mplayer.

Manu




Home | Main Index | Thread Index