From: Issa Gorissen <flop.m@usa.net>
To: linux-media@vger.kernel.org
Cc: Oliver Endriss <o.endriss@gmx.de>
Subject: Re: ngene CI problems
Date: Sun, 24 Apr 2011 01:08:00 +0200 [thread overview]
Message-ID: <4DB35BD0.2040405@usa.net> (raw)
In-Reply-To: <201104232114.31998@orion.escape-edv.de>
On 23/04/11 21:14, Oliver Endriss wrote:
> Basically you should not have to hack anything.
> - Setup the CI as with any conventional device.
> - Write the encrypted stream into sec0.
> - Read the decrypted stream from sec0.
>
> This should work. (Please note that I could do some loopback tests only,
> as I am not watching paytv.)
>
> CU
> Oliver
>
Oliver,
This does not work.
I have launch gnutv like this: 'gnutv -adapter 0 -channels hb.conf -out
dvr -timeout 30 TF1'
Then on dd
tv@tv:~> dd if=188 if=/dev/dvb/adapter0/dvr0 of=/dev/dvb/adapter0/caio0
^C36071+1 records in
36071+0 records out
18468352 bytes (18 MB) copied, 76.4947 s, 241 kB/s
And another dd
tv@tv:~> dd bs=188 if=/dev/dvb/adapter0/caio0 of=test.mpeg
^Cdd: reading `/dev/dvb/adapter0/caio0': Resource temporarily unavailable
1338880+0 records in
1338880+0 records out
251709440 bytes (252 MB) copied, 34.3276 s, 7.3 MB/s
dd: closing input file `/dev/dvb/adapter0/caio0': Bad file descriptor
The first dd reports a more/less correct size for 30sec of encrypted tv
~ 18MB.
But the 2nd dd shows a big generated file out of the device. Plus it
mostly contains the following pattern : lots of FF separated by 47 1F FF 10.
I hope you can guide me to solve this - it is getting painful. Can we
review the code together ? The starting point should be the
ts_write/read methods.
--
Issa
next prev parent reply other threads:[~2011-04-23 23:08 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
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 [this message]
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=4DB35BD0.2040405@usa.net \
--to=flop.m@usa.net \
--cc=linux-media@vger.kernel.org \
--cc=o.endriss@gmx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.