All of lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/freescale-imx/firmware-imx: install the VPU firmware into a valid location
Date: Wed, 13 Jan 2021 20:11:31 +0100	[thread overview]
Message-ID: <9fcc8d9b-eade-1a4b-66f4-e592c73ce41a@gmail.com> (raw)
In-Reply-To: <CAOMZO5BTpG8f=weBKxE9fXtEf3PjGnvs7c979sNBNyKm576ixQ@mail.gmail.com>

Hi Fabio,

Le 13/01/2021 ? 14:29, Fabio Estevam a ?crit?:
> Hi Romain,
> 
> On Wed, Jan 13, 2021 at 10:20 AM Romain Naour <romain.naour@smile.fr> wrote:
> 
>> Ok but it add a 60sec delay when we use the mainline kernel.
> 
> Yes, not a pleasant experience.
> 
> What if we copy the VPU firmware to both locations?
> 
> /lib/firmware/
> /lib/firmware/vpu/
> 
> This way mainline kernel will fetch the VPU firmware faster and NXP
> vendor can also work.
> 

I don't see any difference between NXP vendor and mainline kernel.

See:
https://source.codeaurora.org/external/imx/linux-imx/tree/drivers/media/platform/coda/coda-common.c?h=imx_5.4.70_2.3.0#n2889

Can you check if there is any local change applied to your kernel or a specific
configuration ?

Best regards,
Romain

  reply	other threads:[~2021-01-13 19:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-13 12:08 [Buildroot] [PATCH] package/freescale-imx/firmware-imx: install the VPU firmware into a valid location Fabio Estevam
2021-01-13 13:20 ` Romain Naour
2021-01-13 13:29   ` Fabio Estevam
2021-01-13 19:11     ` Romain Naour [this message]
2021-01-13 19:21       ` Fabio Estevam
2021-01-13 20:02     ` Romain Naour
2021-01-13 20:16       ` Fabio Estevam
2021-01-13 21:01         ` Romain Naour
2021-01-13 22:28           ` Fabio Estevam

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=9fcc8d9b-eade-1a4b-66f4-e592c73ce41a@gmail.com \
    --to=romain.naour@gmail.com \
    --cc=buildroot@busybox.net \
    /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.