All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Vidovic <xtronom@gmail.com>
To: Issa Gorissen <flop.m@usa.net>
Cc: linux-media@vger.kernel.org
Subject: Re: ngene CI problems
Date: Sat, 23 Apr 2011 14:39:41 +0200	[thread overview]
Message-ID: <4DB2C88D.1040200@gmail.com> (raw)
In-Reply-To: <4DB2C20E.1050701@usa.net>

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.

Unfortunately, I don't have nGene (and CXD) chip
documentation, so I stopped solving the problem myself. I
don't want to write software by guessing how HW works.

Best regards,
Martin Vidovic

  reply	other threads:[~2011-04-23 12:37 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 [this message]
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=4DB2C88D.1040200@gmail.com \
    --to=xtronom@gmail.com \
    --cc=flop.m@usa.net \
    --cc=linux-media@vger.kernel.org \
    /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.