Linux Media Controller development
 help / color / mirror / Atom feed
From: Martin Kepplinger <martink@posteo.de>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: mchehab@kernel.org, linux-media@vger.kernel.org
Subject: Re: platform: coda: how to use firmware-imx binary releases?
Date: Thu, 05 Oct 2017 09:43:42 +0200	[thread overview]
Message-ID: <7dd05afd338e81d293d0424e0b8e6b6a@posteo.de> (raw)
In-Reply-To: <1507108964.11691.6.camel@pengutronix.de>

Am 04.10.2017 11:22 schrieb Philipp Zabel:
> Hi Martin,
> 
> 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
> 
> Yes.
> 
>> How do I use this in order to get a VPU firmware blob that the coda 
>> platform driver can work with?
> 
> These are self-extracting shell scripts with an attached compressed tar
> archive. This particular file can be extracted by skipping the first
> 34087 bytes:
> 
> dd if=firmware-imx-5.4.bin bs=34087 skip=1 | tar xjv
> 

thanks!

>> (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 which would
>> be a good place for documenting how to use these binaries too)
> 
> Thank you for pointing this out, the device tree binding docs for coda
> are indeed missing.
> I'm not sure the device tree binding docs are the right place to
> document driver and firmware though. For that, adding a coda.rst entry
> to Documentation/media/v4l-drivers would probably be a better place.
> 

True. That'd be great. Some firmware-handling and maybe even firmware
version changelogs would definitely be useful.


I'm running a little off-topic here, but with the newest firmware too, 
my
coda driver says "Video Data Order Adapter: Disabled" when started
by video playback via v4l2.

(imx6, running linux 4.14-rc3, imx-vdoa is probed and never removed,
a dev_info "probed" would maybe be useful for others too?)

It supsequently fails with

cma: cma_alloc: alloc failed, req-size: 178 pages, ret: -12

which may or may not be related to having the vdoa (is it?), but 
shouldn't
the VDOA module be active by default?

# cat /sys/module/coda/parameters/disable_vdoa
0

thanks

                                 martin

  reply	other threads:[~2017-10-05  7:43 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 [this message]
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 ` platform: coda: how to use firmware-imx binary releases? Philipp Zabel
2017-10-05 16:00   ` 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=7dd05afd338e81d293d0424e0b8e6b6a@posteo.de \
    --to=martink@posteo.de \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox