From: Fabio Estevam <festevam@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 09:08:22 -0300 [thread overview]
Message-ID: <20210113120822.327-1-festevam@gmail.com> (raw)
The mainline kernel searches the coda VPU firmware inside the following
locations [1]:
/lib/firmware/
/lib/firmware/vpu/
Currently Buildroot installs the coda firmware into /lib/firmware/imx/vpu,
which is not a valid location.
Fix it to install the coda firmwares into /lib/firmware/vpu/ which
is a valid path for both mainline and NXP vendor kernels.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=8af7779f3cbc1f6720d15f00abc797493710d1ab
Reported-by: Romain Naour <romain.naour@gmail.com>
Signed-off-by: Fabio Estevam <festevam@gmail.com>
---
package/freescale-imx/firmware-imx/firmware-imx.mk | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/freescale-imx/firmware-imx/firmware-imx.mk b/package/freescale-imx/firmware-imx/firmware-imx.mk
index 7d1f42f1d87b..f65614c9a79c 100644
--- a/package/freescale-imx/firmware-imx/firmware-imx.mk
+++ b/package/freescale-imx/firmware-imx/firmware-imx.mk
@@ -116,9 +116,9 @@ endif
FIRMWARE_IMX_VPU_FW_NAME = $(call qstrip,$(BR2_PACKAGE_FIRMWARE_IMX_VPU_FW_NAME))
ifneq ($(FIRMWARE_IMX_VPU_FW_NAME),)
define FIRMWARE_IMX_INSTALL_TARGET_VPU_FW
- mkdir -p $(TARGET_DIR)/lib/firmware/imx/vpu
+ mkdir -p $(TARGET_DIR)/lib/firmware/vpu
cp $(@D)/firmware/vpu/vpu_fw_$(FIRMWARE_IMX_VPU_FW_NAME)*.bin \
- $(TARGET_DIR)/lib/firmware/imx/vpu/
+ $(TARGET_DIR)/lib/firmware/vpu/
endef
endif
--
2.17.1
next reply other threads:[~2021-01-13 12:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 12:08 Fabio Estevam [this message]
2021-01-13 13:20 ` [Buildroot] [PATCH] package/freescale-imx/firmware-imx: install the VPU firmware into a valid location Romain Naour
2021-01-13 13:29 ` Fabio Estevam
2021-01-13 19:11 ` Romain Naour
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=20210113120822.327-1-festevam@gmail.com \
--to=festevam@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.