From: Issa Gorissen <flop.m@usa.net>
To: xtronom@gmail.com
Cc: linux-media@vger.kernel.org
Subject: ngene CI problems
Date: Sat, 23 Apr 2011 00:16:56 +0200 [thread overview]
Message-ID: <4DB1FE58.20006@usa.net> (raw)
In-Reply-To: <4D74E28A.6030302@gmail.com>
> Hi all!
>
> I'm trying to make the DVB_DEVICE_SEC approach work, however I'm
> experiencing certain problems with the following setup:
>
> Software:
> Linux 2.6.34.8 (vanilla)
> drivers from http://linuxtv.org/hg/~endriss/v4l-dvb/ <http://linuxtv.org/hg/%7Eendriss/v4l-dvb/>
>
> Hardware:
> Digital Devices CineS2 + CI Module
>
> Problems:
>
> - Packets get lost in SEC device:
>
> I write complete TS to SEC, but when reading from SEC there are
> discontinuities on the CC.
>
> - SEC device generates NULL packets (ad infinitum):
>
> When reading from SEC, NULL packets are read and interleaved with
> expected packets. They can be even read with dd(1) when nobody is
> writing to SEC and even when CAM is not ready.
>
> - SEC device blocks on CAM re-insertion:
>
> When CAM is removed from the slot and inserted again, all read()
> operations just hang. Rebooting resolves the problem.
>
> - SEC device does not respect O_NONBLOCK:
>
> In connection to the previous problem, SEC device blocks even if opened
> with O_NONBLOCK.
>
> Best regards,
> Martin Vidovic
Hi,
Running a bunch of test with gnutv and a DuoFLEX S2.
I saw the same problem concerning the decryption with a CAM.
I'm running kern 2.6.39 rc 4 with the latest patches from Oliver. Also
applied the patch moving from SEC to CAIO.
I would run gnutv like 'gnutv -out stdout channelname >
/dev/dvb/adapter0/caio0' and then 'cat /dev/dvb/adapter0/caio0 | mplayer -'
Mplayer would complain the file is invalid. Simply running simply 'cat
/dev/dvb/adapter0/caio0' will show me the same data pattern over and over.
Anyone using ngene based card with a CAM running successfully ?
--
Issa
next prev parent reply other threads:[~2011-04-22 22:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 13:50 ngene CI problems Martin Vidovic
2011-04-22 22:16 ` Issa Gorissen [this message]
2011-04-23 10:19 ` Issa Gorissen
2011-05-03 6:48 ` Sébastien RAILLARD (COEXSI)
2011-04-23 11:37 ` Martin Vidovic
2011-04-23 12:11 ` Issa Gorissen
2011-04-23 12:39 ` Martin Vidovic
2011-04-23 13:29 ` Issa Gorissen
2011-04-23 17:40 ` Oliver Endriss
2011-04-23 18:56 ` Issa Gorissen
2011-04-23 19:14 ` Oliver Endriss
2011-04-23 19:52 ` Issa Gorissen
2011-04-23 23:08 ` Issa Gorissen
2011-05-11 18:59 ` Oliver Endriss
2011-05-12 11:30 ` Issa Gorissen
2011-05-12 20:28 ` Issa Gorissen
2011-05-12 22:34 ` Oliver Endriss
2011-05-22 12:48 ` Martin Vidovic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DB1FE58.20006@usa.net \
--to=flop.m@usa.net \
--cc=linux-media@vger.kernel.org \
--cc=xtronom@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox