[vdr] Re: SV: CAM support, was Improved CAM support in VDR

[Micael Beronius <micael.beronius@telia.com>]

Hello Klaus,

Sunday, January 12, 2003, 1:31:31 PM, you wrote:

KS> Klaus Schmidinger wrote:
>> 
>> micael.beronius@telia.com wrote:
>> >
>> > I tried once more. I now pulled the card and re-seated it. I then got;
>> >
>> > slot 0  state 0003
>> > slot 1  state 0000
>> > -->> 00 01 82 01 01
>> > -->> 00 01 82 01 01
>> > -->> 00 01 82 01 01
>> > -->> 00 01 82 01 01
>> > -->> 00 01 82 01 01
>> > -->> 00 01 82 01 01
>> > -->> 00 01 82 01 01
>> > -->> 00 01 82 01 01
>> > -->> 00 01 82 01 01
>> > -->> 00 01 82 01 01
>> > -->> 00 01 82 01 01
>> >
>> >  Micael
>> 
>> Ok so now the CAM is detected to be "present", but still no response is
>> received from it. As I stated in my previous reply I assume the CA_RESET
>> is not working...

KS> I guess I just found something here: apparently the parameter to the CA_RESET
KS> ioctl() call is not the slot index, but rather flag word containign a '1' bit for
KS> every slot that shall be reset. Please give the new ftp://ftp.cadsoft.de/vdr/Developer/ci.c
KS> a try, in which I have changed this (there may be lots of "slot 0  state 0001" messages at
KS> stdout, but maybe this change activates the actual CA_RESET, which previously wasn't
KS> executed since the slot parameter was '0').

Hmmm.. I get very strange results here. I get sometimes;

(I have only a CAM in the lower slot (slot 0 I think))

slot 0 state 0001
slot 1 state 0001
slot 1 state 0000
slot 1 state 0001
-->> 00 01 82 01 01
-->> 00 01 82 01 01
-->> 00 01 82 01 01
-->> 00 01 82 01 01
-->> 00 01 82 01 01
-->> 00 01 82 01 01
-->> 00 01 82 01 01
.. and so on ..


-- 

 Micael



-- 
Info:
To unsubscribe send a mail to listar@linuxtv.org with "unsubscribe vdr" as subject.