From: Philipp Zabel <p.zabel@pengutronix.de>
To: Martin Kepplinger <martink@posteo.de>, mchehab@kernel.org
Cc: linux-media@vger.kernel.org
Subject: Re: platform: coda: how to use firmware-imx binary releases?
Date: Thu, 05 Oct 2017 17:45:40 +0200 [thread overview]
Message-ID: <1507218340.8473.19.camel@pengutronix.de> (raw)
In-Reply-To: <ef7cc5b91829f383842a1e4692af5b07@posteo.de>
On Wed, 2017-10-04 at 10:44 +0200, Martin Kepplinger wrote:
> Hi,
>
> Commit
>
> be7f1ab26f42 media: coda: mark CODA960 firmware versions 2.3.10
> and
> 3.1.1 as supported
>
> says firmware version 3.1.1 revision 46072 is contained in
> "firmware-imx-5.4.bin", that's probably
>
> sha1 78a416ae88ff01420260205ce1d567f60af6847e firmware-imx-
> 5.4.bin
>
> How do I use this in order to get a VPU firmware blob that the coda
> platform driver can work with?
>
>
>
> (Maybe it'd be worth adding some short documentation on this. There
> doesn't seem to be a devicetree bindings doc for coda in
> Documentation/devicetree/bindings/media
I was mistaken, Documentation/devicetree/bindings/media/coda.txt exists.
It was added in commit 657eee7d25fb ("media: coda: use genalloc API").
regards
Philipp
next prev parent reply other threads:[~2017-10-05 15:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 8:44 platform: coda: how to use firmware-imx binary releases? Martin Kepplinger
2017-10-04 9:22 ` Philipp Zabel
2017-10-05 7:43 ` Martin Kepplinger
2017-10-05 8:19 ` Philipp Zabel
2017-10-05 11:54 ` platform: coda: how to use firmware-imx binary releases? / how to use VDOA on imx6? Martin Kepplinger
2017-10-05 14:10 ` Nicolas Dufresne
2017-10-05 14:30 ` Martin Kepplinger
2017-10-05 15:45 ` Philipp Zabel [this message]
2017-10-05 16:00 ` platform: coda: how to use firmware-imx binary releases? 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=1507218340.8473.19.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=linux-media@vger.kernel.org \
--cc=martink@posteo.de \
--cc=mchehab@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.