All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gaëtan Carlier" <gcembed@gmail.com>
To: linux-media@vger.kernel.org
Cc: javier Martin <javier.martin@vista-silicon.com>,
	Fabio Estevam <festevam@gmail.com>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Fabio Estevam <fabio.estevam@freescale.com>
Subject: Re: [CODA] Info about internal buffers in CodaDX6
Date: Mon, 16 Jun 2014 10:49:23 +0200	[thread overview]
Message-ID: <539EAF93.1020700@gmail.com> (raw)
In-Reply-To: <538D8804.2010900@gmail.com>

Hello,
No one can give me more information about these registers ?
Thank you.
Bets regards,
Gaëtan Carlier.

On 06/03/2014 10:32 AM, Gaëtan Carlier wrote:
> Dear,
> I am back to add support of h.264 decoding using Coda DX6 on i.MX27
> (after long months of inactivity).
> I base my work on driver from linux 2.6.22 (libvpu) and last coda.c from
> linux-next/master.
>
> When I send DEC_SEQ_INIT command, it fails but I don't know why.
> 1) Which internal buffers do Coda DX6 really have/used for decoding
> PARABUF, WORKBUF, PSBUF, ...) ?
> 2) What is their role ?
> 3) I see in some code that there is a command
> CODA_RET_DEC_SEQ_ERR_REASON (0x1E0), which has the same opcode has
> RET_DEC_SEQ_NEXT_FRAME_NUM, but when I run this command after
> DEC_SEQ_INIT, it returns 1 that does not seems to be correct error
> (regarding RetCode enum in vpu_lib.h in libvpu)
>
> Code is based on 3.6.0 kernel revision with some backport from more
> recent version of coda.c
>
> Thanks a lot for your help.
> Best regards,
> Gaëtan Carlier.


      reply	other threads:[~2014-06-16  8:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-03  8:32 [CODA] Info about internal buffers in CodaDX6 Gaëtan Carlier
2014-06-16  8:49 ` Gaëtan Carlier [this message]

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=539EAF93.1020700@gmail.com \
    --to=gcembed@gmail.com \
    --cc=fabio.estevam@freescale.com \
    --cc=festevam@gmail.com \
    --cc=javier.martin@vista-silicon.com \
    --cc=linux-media@vger.kernel.org \
    --cc=p.zabel@pengutronix.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.