From: Fabio Estevam <festevam@gmail.com>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Kamil Debski <k.debski@samsung.com>,
linux-media <linux-media@vger.kernel.org>,
Philipp Zabel <philipp.zabel@gmail.com>
Subject: Re: [PATCH] [media] coda: add support for native order firmware files with Freescale header
Date: Wed, 17 Feb 2016 16:01:51 -0200 [thread overview]
Message-ID: <CAOMZO5COpeaX_-YHL=sVDPDMG6twp2ZbEMUyvqab+hRewpmdUA@mail.gmail.com> (raw)
In-Reply-To: <1455719247.3336.23.camel@pengutronix.de>
On Wed, Feb 17, 2016 at 12:27 PM, Philipp Zabel <p.zabel@pengutronix.de> wrote:
> Hi Mauro,
>
> Am Mittwoch, den 17.02.2016, 11:35 -0200 schrieb Mauro Carvalho Chehab:
>> Em Wed, 17 Feb 2016 14:21:10 +0100
>> Philipp Zabel <p.zabel@pengutronix.de> escreveu:
>>
>> > Freescale distribute their VPU firmware files with a 16 byte header
>> > in BIT processor native order. This patch allows to detect the header
>> > and to reorder the firmware on the fly.
>> > With this patch it should be possible to use the distributed
>> > vpu_fw_imx{53,6q,6d}.bin files directly after renaming them to
>> > v4l-coda*-imx{53,6q,6dl}.bin.
>>
>> IMHO, the best would be to add another patch to support the files with
>> their original names, falling back to v4l-coda*. We do this on other
>> drivers where more than one firmware file could be used.
>
> thank you for the suggestion. I'll follow up with another patch that
> also supports the firmware file names as they are distributed.
That would be nice. Thanks, Philipp
prev parent reply other threads:[~2016-02-17 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 13:21 [PATCH] [media] coda: add support for native order firmware files with Freescale header Philipp Zabel
2016-02-17 13:35 ` Mauro Carvalho Chehab
2016-02-17 14:27 ` Philipp Zabel
2016-02-17 18:01 ` Fabio Estevam [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='CAOMZO5COpeaX_-YHL=sVDPDMG6twp2ZbEMUyvqab+hRewpmdUA@mail.gmail.com' \
--to=festevam@gmail.com \
--cc=k.debski@samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=p.zabel@pengutronix.de \
--cc=philipp.zabel@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).