Paul Sokolovsky wrote: > > ----- Original Message ----- From: "Manu Abraham" <manu@xxxxxxxxxxx> > To: "Allan Stirling" <Dibblahdvb0042@xxxxxxxxxx> > Cc: <linux-dvb@xxxxxxxxxxx> > Sent: Sunday, July 03, 2005 6:58 PM > Subject: Re: [linux-dvb] TechniSat Skystar 1 CI (Twinhan clone) ca_zap > notworking > > >> Allan Stirling wrote: >> >>> Manu Abraham wrote: >>> >>>> Paul Sokolovsky wrote: >>>> >>>>> >>>>> Is there anything wrong in this output? >>>>> >>>>> And another question is: why there is only one element in >>>>> parse_streams of type 2 (pid 320)? Where is the second one of type >>>>> 4 (pid 400)? In some previous posts I saw all the elements in >>>>> ca_zap's output. >>>>> >>>> >>>> Due to the bugs, the parser has to be reworked. >>>> >>> Glad (in a way) to hear this. Is there anything we can do to help? >>> (packet dumps, etc) >>> >> >> Testing would be required as soon as things are assumed to be fixed .. > > > I'll be happy to help. Until then - is it possible to get some > explanation how to construct a correct CA_message assuming that I am > already have all required data? For example - I am using VLC and there Ok, here it goes.. For constructing a CA_MESSAGE it is as simple as constructing a valid EN50221 CA_PMT object. Where exactly it writes to the device you can take a look at en50221_hlci.c. write_to_slot() Can't spend too much of a time with the computer, as having a terrible eye infection.. > is a CAM support in latest versions. It is not working with Twinhan > because (as I understand) VLC uses different API (low-level?) but all > needed information is already prepared. > Reversing the processed information might be a herculean task, so i would say that a write from scratch to create a CA_PMT object is the best .. Manu
