From: Philipp Zabel <p.zabel@pengutronix.de>
To: Martin Kepplinger <martink@posteo.de>
Cc: linux-media@vger.kernel.org
Subject: Re: media: coda: sources of coda_regs.h?
Date: Wed, 22 Nov 2017 11:40:00 +0100 [thread overview]
Message-ID: <1511347200.17007.1.camel@pengutronix.de> (raw)
In-Reply-To: <15f29890-d029-95a3-c00d-73ed566ff172@posteo.de>
Hi Martin,
On Thu, 2017-11-09 at 23:14 +0100, Martin Kepplinger wrote:
> Hi Philipp,
>
> As I'm reading up on the coda driver a little, I can't seem to find the
> vendor's sources for the coda_regs.h definitions. Could you point me to
> them?
I don't know for sure what information Javier based the CodaDx6 register
names on, but I assume that he used the old LGPLed i.MX VPU libraries
that Freescale once distributed. At least that's what I looked at for
the CODA960 additions: The BSP "L3.0.35_12.09.01.01_GA_source.tar.gz"
contained a tarball "pkgs/imx-lib-12.09.01.tar.gz" with a header file
"imx-lib-12.09.01/vpu/vpu_reg.h" inside. I believe the current BSP
versions distributed by NXP do not include this library anymore.
regards
Philipp
next prev parent reply other threads:[~2017-11-22 10:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 22:14 media: coda: sources of coda_regs.h? Martin Kepplinger
2017-11-22 10:40 ` Philipp Zabel [this message]
2017-11-22 13:47 ` Martin Kepplinger
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=1511347200.17007.1.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=linux-media@vger.kernel.org \
--cc=martink@posteo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox