Re: ngene CI problems

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

 



On 23/04/11 14:39, Martin Vidovic wrote:
> Hi,
>> Okay, but have you managed to decode any channel yet ?
>>   
> Yes, I managed to descramble programmes without any problem.
>> I find some code odd, maybe you can take a look as well...
>>
>> init_channel in ngene-core.c creates the device sec0/caio0 with the
>> struct ngene_dvbdev_ci. In ngene-dvb.c you can see that this struct
>> declares the methods ts_read/ts_write to handle r/w operations on the
>> device sec0/caio0.
>>
>> Now take a look at those methods (ts_read/ts_write). I don't see how
>> they 'connect' to the file cxd2099.c which contains the methods handling
>> the i/o to the cam
> They don't connect explicitly. Transfers are done implicitly
> through nGene ring-buffers. See demux_tasklet(). CXD code
> seems to be used only for CAM commands and setup (only) of
> data transfers.

I have taken a look into the ddbrigde module code from
<http://linuxtv.org/hg/~endriss/ngene-octopus-test/rev/6b400d63c481>

The ts_read/ts_write methods are different from the ngene module's. So I
guess were are having entirely different problems.
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux