Skip to contentSkip to conversation

Bump NXP BSP components to 5.4.70_2.3.0

PATCH New Stephane Viau 6 participants 26 messages Jan 5, 2021 – Jan 17, 2021 Arm i.MX and Layerscape

lore
Share & tools
lore
#0 lore raw

v2 cover Bump NXP BSP components to 5.4.70_2.3.0

Hi,

Here is the patch set to bump freescale-imx configs and vital packages to match the latest NXP Linux release: 5.4.70_2.3.0.
Some configs are run-tested, some aren't... but all are build-tested.

Notes:
1) other components update (e.g.: imx-{codec,kobs,parser,vpu*,...}) are not part of this patch set.
2) gpu-viv-* components are already updated to 6.4.3.p1.0 (thanks, Gary!)

BR,
Stephane.

Stephane Viau (8):
package/freescale-imx/firmware-imx: bump version to 8.10 package/freescale-imx/imx-sc-firmware: bump version to 1.7.0 package/freescale-imx/imx-seco: bump version to 3.7.4 package/imx-mkimage: bump to version rel_imx_5.4.70_2.3.0 configs/freescale_imx6*: bump BSP components to 5.4.70_2.3.0 configs/freescale_imx7dsabresd: bump BSP components to 5.4.70_2.3.0 configs/freescale_imx8m*: bump BSP components to 5.4.70_2.3.0 configs/freescale_imx8*: bump BSP components to 5.4.70_2.3.0

 configs/freescale_imx6dlsabreauto_defconfig               | 4 ++--
 configs/freescale_imx6dlsabresd_defconfig                 | 4 ++--
 configs/freescale_imx6qsabreauto_defconfig                | 4 ++--
 configs/freescale_imx6qsabresd_defconfig                  | 4 ++--
 configs/freescale_imx6sxsabresd_defconfig                 | 4 ++--
 configs/freescale_imx6ullevk_defconfig                    | 4 ++--
 configs/freescale_imx7dsabresd_defconfig                  | 4 ++--
 configs/freescale_imx8mmevk_defconfig                     | 8 ++++----
 configs/freescale_imx8mnevk_defconfig                     | 6 +++---
 configs/freescale_imx8mqevk_defconfig                     | 6 +++---
 configs/freescale_imx8qmmek_defconfig                     | 6 +++---
 configs/freescale_imx8qxpmek_defconfig                    | 6 +++---
 package/freescale-imx/firmware-imx/firmware-imx.hash      | 6 +++---
 package/freescale-imx/firmware-imx/firmware-imx.mk        | 2 +-
 .../freescale-imx/imx-sc-firmware/imx-sc-firmware.hash    | 6 +++---
 package/freescale-imx/imx-sc-firmware/imx-sc-firmware.mk  | 2 +-
 package/freescale-imx/imx-seco/imx-seco.hash              | 6 +++---
 package/freescale-imx/imx-seco/imx-seco.mk                | 2 +-
 package/imx-mkimage/imx-mkimage.hash                      | 2 +-
 package/imx-mkimage/imx-mkimage.mk                        | 2 +-
 20 files changed, 44 insertions(+), 44 deletions(-)
Signature · 1 line
2.29.2
#1 lore raw

PATCH v2 1/8 package/freescale-imx/firmware-imx: bump version to 8.10

- Same version as NXP release 5.4.70-2.3.0
- EULA/COPYING: update to LA_OPT_NXP_Software_License v17

---
v2:
- Add "EULA/COPYING: update to LA_OPT_NXP_Software_License v17" in commit log (Gary)

---
 package/freescale-imx/firmware-imx/firmware-imx.hash | 6 +++---
 package/freescale-imx/firmware-imx/firmware-imx.mk   | 2 +-
 2 files changed, 4 insertions(+), 4 deletions(-)
package/freescale-imx/firmware-imx/firmware-imx.hash +3 -3
index 3230677d49..0a717d40f5 100644
@@ -1,4 +1,4 @@
 # Locally calculated
-sha256  a72f70fd2ecaa58800bb88ed672fddc322ab9843ee7777eb89b82016b0aa3614  firmware-imx-8.9.bin
-sha256  a39da2e94bd8b99eaac4325633854620ea3a55145259c3a7748c610a80714cfc  EULA
-sha256  69cbb76b3f10ac5a8c36f34df7bbdf50825815560c00a946fff2922365ef01a2  COPYING
+sha256  2b70f169d4065b2a7ac7a676afe24636128bd2dacc9f5230346758c3b146b2be  firmware-imx-8.10.bin
+sha256  72edc2072c86d93aa1993d15d4d19d96270af3749b0108995ad50c81d1461f52  EULA
+sha256  9c16421e7c702f56756650b8ac954d34556327e598a8666e6e8f4eb3a1aa95f1  COPYING
package/freescale-imx/firmware-imx/firmware-imx.mk +1 -1
index 7d1f42f1d8..b33ffb7ee8 100644
@@ -4,7 +4,7 @@
 #
 ################################################################################
 
-FIRMWARE_IMX_VERSION = 8.9
+FIRMWARE_IMX_VERSION = 8.10
 FIRMWARE_IMX_SITE = $(FREESCALE_IMX_SITE)
 FIRMWARE_IMX_SOURCE = firmware-imx-$(FIRMWARE_IMX_VERSION).bin
 
Signature · 1 line
2.29.2
#2 lore raw

PATCH v2 1/8 package/freescale-imx/firmware-imx: bump version to 8.10

Hello,

Le 05/01/2021 ? 16:24, Stephane Viau a ?crit?:

Quoted 5 lines

- Same version as NXP release 5.4.70-2.3.0
- EULA/COPYING: update to LA_OPT_NXP_Software_License v17

Not related to this patch, but why those firmware are installed to $(TARGET_DIR)/lib/firmware/imx ?

Because without any change I get:

coda 2040000.vpu: Direct firmware load for vpu/vpu_fw_imx6q.bin failed with error -2 coda 2040000.vpu: Falling back to sysfs fallback for: vpu/vpu_fw_imx6q.bin coda 2040000.vpu: Direct firmware load for v4l-coda960-imx6q.bin failed with error -2
coda 2040000.vpu: Falling back to sysfs fallback for: v4l-coda960-imx6q.bin coda 2040000.vpu: firmware request failed

It seems that vpu directory is expected to be in "firmware" directory:
$(TARGET_DIR)/lib/firmware/vpu

see:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=8af7779f3cbc1f6720d15f00abc797493710d1ab

At least we have to create a simlink:
/lib/firmware/imx/vpu -> /lib/firmware/vpu

or set fw_path_para in the kernel cmdline:
firmware_class.path=/lib/firmware/imx/

Best regards,
Romain

Quoted 35 lines

---
v2:
- Add "EULA/COPYING: update to LA_OPT_NXP_Software_License v17" in commit log (Gary)

---
 package/freescale-imx/firmware-imx/firmware-imx.hash | 6 +++---
 package/freescale-imx/firmware-imx/firmware-imx.mk   | 2 +-
 2 files changed, 4 insertions(+), 4 deletions(-)
package/freescale-imx/firmware-imx/firmware-imx.hash +3 -3
index 3230677d49..0a717d40f5 100644
@@ -1,4 +1,4 @@
 # Locally calculated
-sha256  a72f70fd2ecaa58800bb88ed672fddc322ab9843ee7777eb89b82016b0aa3614  firmware-imx-8.9.bin
-sha256  a39da2e94bd8b99eaac4325633854620ea3a55145259c3a7748c610a80714cfc  EULA
-sha256  69cbb76b3f10ac5a8c36f34df7bbdf50825815560c00a946fff2922365ef01a2  COPYING
+sha256  2b70f169d4065b2a7ac7a676afe24636128bd2dacc9f5230346758c3b146b2be  firmware-imx-8.10.bin
+sha256  72edc2072c86d93aa1993d15d4d19d96270af3749b0108995ad50c81d1461f52  EULA
+sha256  9c16421e7c702f56756650b8ac954d34556327e598a8666e6e8f4eb3a1aa95f1  COPYING
package/freescale-imx/firmware-imx/firmware-imx.mk +1 -1
index 7d1f42f1d8..b33ffb7ee8 100644
@@ -4,7 +4,7 @@
 #
 ################################################################################
 
-FIRMWARE_IMX_VERSION = 8.9
+FIRMWARE_IMX_VERSION = 8.10
 FIRMWARE_IMX_SITE = $(FREESCALE_IMX_SITE)
 FIRMWARE_IMX_SOURCE = firmware-imx-$(FIRMWARE_IMX_VERSION).bin
 
reviewer
#3 lore raw

PATCH v2 1/8 package/freescale-imx/firmware-imx: bump version to 8.10

Hi Romain,

Quoted 15 lines · Romain Naour

Not related to this patch, but why those firmware are installed to $(TARGET_DIR)/lib/firmware/imx ?

Because without any change I get:

coda 2040000.vpu: Direct firmware load for vpu/vpu_fw_imx6q.bin failed with error -2 coda 2040000.vpu: Falling back to sysfs fallback for: vpu/vpu_fw_imx6q.bin coda 2040000.vpu: Direct firmware load for v4l-coda960-imx6q.bin failed with error -2
coda 2040000.vpu: Falling back to sysfs fallback for: v4l-coda960-imx6q.bin coda 2040000.vpu: firmware request failed

It seems that vpu directory is expected to be in "firmware" directory:
$(TARGET_DIR)/lib/firmware/vpu

Quoted 8 lines

see:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=8af7779f3cbc1f6720d15f00abc797493710d1ab

At least we have to create a simlink:
/lib/firmware/imx/vpu -> /lib/firmware/vpu

or set fw_path_para in the kernel cmdline:
firmware_class.path=/lib/firmware/imx/

I notice the same here on a imx53.

Then I tried to change the VPU path like this:

package/freescale-imx/firmware-imx/firmware-imx.mk +0 -0
@@ -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

,but the VPU firmware is still not found:

[    9.237801] coda 63ff4000.vpu: IRQ bit not found
[    9.291801] coda 63ff4000.vpu: Direct firmware load for
vpu_fw_imx53.bin failed with error -2
[    9.300646] coda 63ff4000.vpu: Falling back to sysfs fallback for:

vpu_fw_imx53.bin
done
Saving random seed: [ 9.997216] random: dd: uninitialized urandom
read (512 bytes read)
OK
Starting network: OK

Welcome to Buildroot
buildroot login: root

# ls /lib/firmware/vpu/vpu_fw_imx53.bin
/lib/firmware/vpu/vpu_fw_imx53.bin
#

Any ideas?

Thanks,

Fabio Estevam

reviewer
#4 lore raw

PATCH v2 1/8 package/freescale-imx/firmware-imx: bump version to 8.10

Hi Romain,

Quoted 1 line · Fabio Estevam

I notice the same here on a imx53.

It works for me if I change it like this:

package/freescale-imx/firmware-imx/firmware-imx.mk +0 -0
@@ -116,9 +116,8 @@ 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

        cp $(@D)/firmware/vpu/vpu_fw_$(FIRMWARE_IMX_VPU_FW_NAME)*.bin \

- $(TARGET_DIR)/lib/firmware/imx/vpu/
+ $(TARGET_DIR)/lib/firmware/
endef
endif

[    9.727308] coda 63ff4000.vpu: IRQ bit not found
[    9.848458] coda 63ff4000.vpu: Initialized CODA7541.
[    9.853967] coda 63ff4000.vpu: Firmware version: 1.4.50
[    9.937682] coda 63ff4000.vpu: encoder registered as video5
[    9.962135] coda 63ff4000.vpu: decoder registered as video6
[    9.985276] coda 63ff4000.vpu: encoder registered as video7
[   10.018420] coda 63ff4000.vpu: decoder registered as video8

Would the change above be acceptable? If so, I can submit it.

Thanks

#5 lore raw

PATCH v2 1/8 package/freescale-imx/firmware-imx: bump version to 8.10

Hi Fabio,

Le 13/01/2021 ? 01:43, Fabio Estevam a ?crit?:

Quoted 11 lines

Hi Romain,

Quoted 1 line · Fabio Estevam

I notice the same here on a imx53.

It works for me if I change it like this:

package/freescale-imx/firmware-imx/firmware-imx.mk endif · line 121

Quoted 8 lines
package/freescale-imx/firmware-imx/firmware-imx.mk +1 -2
@@ -116,9 +116,8 @@ 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
        cp $(@D)/firmware/vpu/vpu_fw_$(FIRMWARE_IMX_VPU_FW_NAME)*.bin \
-               $(TARGET_DIR)/lib/firmware/imx/vpu/
+               $(TARGET_DIR)/lib/firmware/

Here you're installing the firmware in the first supported firmware path, this allow to load the firmware on the first try.

Quoted 12 lines
package/freescale-imx/firmware-imx/firmware-imx.mk +0 -0
 endef
 endif

[    9.727308] coda 63ff4000.vpu: IRQ bit not found
[    9.848458] coda 63ff4000.vpu: Initialized CODA7541.
[    9.853967] coda 63ff4000.vpu: Firmware version: 1.4.50
[    9.937682] coda 63ff4000.vpu: encoder registered as video5
[    9.962135] coda 63ff4000.vpu: decoder registered as video6
[    9.985276] coda 63ff4000.vpu: encoder registered as video7
[   10.018420] coda 63ff4000.vpu: decoder registered as video8
Quoted 1 line

Would the change above be acceptable? If so, I can submit it.

I'm not sure if we should install the vpu firmware directly in "/lib/firmware/" or "/lib/firmware/vpu". Feel free to submit a patch to discuss about this change.

Thanks!

Best regards,
Romain

Quoted 3 lines

Thanks

reviewer
#6 lore raw

PATCH v2 1/8 package/freescale-imx/firmware-imx: bump version to 8.10

Hi Romain,

Quoted 2 lines · Romain Naour

I'm not sure if we should install the vpu firmware directly in "/lib/firmware/" or "/lib/firmware/vpu". Feel free to submit a patch to discuss about this change.

Mainline kernels search first inside /lib/firmware and then inside /lib/firmware/vpu

The NXP BSPs search the VPU firmware inside /lib/firmware/vpu, so I think we need to use this location, which can make vendor and mainline kernels happy.

However, it is not working for me if I place it inside /lib/firmware/vpu with a 5.10 kernel.

I will investigate this when I have a chance.

Thanks

#7 lore raw

PATCH v2 1/8 package/freescale-imx/firmware-imx: bump version to 8.10

Hello Fabio,

Le 13/01/2021 ? 12:16, Fabio Estevam a ?crit?:

Quoted 7 lines

Hi Romain,

Quoted 2 lines · Romain Naour

I'm not sure if we should install the vpu firmware directly in "/lib/firmware/" or "/lib/firmware/vpu". Feel free to submit a patch to discuss about this change.

Quoted 6 lines

Mainline kernels search first inside /lib/firmware and then inside /lib/firmware/vpu

The NXP BSPs search the VPU firmware inside /lib/firmware/vpu, so I think we need to use this location, which can make vendor and mainline kernels happy.

Ok for me.

Quoted 5 lines

However, it is not working for me if I place it inside /lib/firmware/vpu with a 5.10 kernel.

I will investigate this when I have a chance.

I'm using a kernel 5.10.6 on imx6 (savrelite)

Before moving vpu directory:

# dmesg | grep coda
[   11.805864] coda 2040000.vpu: Direct firmware load for vpu_fw_imx6q.bin
failed with error -2
[   11.814654] coda 2040000.vpu: Falling back to sysfs fallback for:
vpu_fw_imx6q.bin
[   74.713145] coda 2040000.vpu: Direct firmware load for vpu/vpu_fw_imx6q.bin
failed with error -2
[   74.722182] coda 2040000.vpu: Falling back to sysfs fallback for:
vpu/vpu_fw_imx6q.bin
[  136.152801] coda 2040000.vpu: Direct firmware load for v4l-coda960-imx6q.bin
failed with error -2
[  136.161972] coda 2040000.vpu: Falling back to sysfs fallback for:
v4l-coda960-imx6q.bin
[  197.590983] coda 2040000.vpu: firmware request failed
# uname -a
Linux buildroot 5.10.6 #1 SMP Tue Jan 12 15:47:33 CET 2021 armv7l GNU/Linux

After moving vpu directory to /lib/firmware/vpu and reboot:

# dmesg | grep coda
[   12.206789] coda 2040000.vpu: Direct firmware load for vpu_fw_imx6q.bin
failed with error -2
[   12.215594] coda 2040000.vpu: Falling back to sysfs fallback for:
vpu_fw_imx6q.bin
[   74.749483] coda 2040000.vpu: Using fallback firmware vpu/vpu_fw_imx6q.bin
[   74.772346] coda 2040000.vpu: Firmware code revision: 46076
[   74.777985] coda 2040000.vpu: Initialized CODA960.
[   74.783247] coda 2040000.vpu: Firmware version: 3.1.1
[   74.790424] coda 2040000.vpu: encoder registered as video8
[   74.796587] coda 2040000.vpu: decoder registered as video9
[   74.809556] coda 2040000.vpu: encoder registered as video10
[   74.823956] coda 2040000.vpu: decoder registered as video11
# uname -a
Linux buildroot 5.10.6 #1 SMP Tue Jan 12 15:47:33 CET 2021 armv7l GNU/Linux

I don't know why it doesn't work for you.

Best regards,
Romain

Quoted 7 lines

Thanks
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

reviewer
#8 lore raw

PATCH v2 1/8 package/freescale-imx/firmware-imx: bump version to 8.10

Hi Romain,

Quoted 1 line · Romain Naour

I don't know why it doesn't work for you.

It's working now. I just had to wait longer :-) The second path is searched after approximately 75 seconds.

I will submit a patch changing the VPU path to /lib/firmware/vpu.

Thanks

#9 lore raw

PATCH v2 1/8 package/freescale-imx/firmware-imx: bump version to 8.10

In reply to Fabio Estevam

Hello Fabio,

Le 13/01/2021 ? 01:27, Fabio Estevam a ?crit?:

Quoted 47 lines

Hi Romain,

Quoted 15 lines · Romain Naour

Not related to this patch, but why those firmware are installed to $(TARGET_DIR)/lib/firmware/imx ?

Because without any change I get:

coda 2040000.vpu: Direct firmware load for vpu/vpu_fw_imx6q.bin failed with error -2 coda 2040000.vpu: Falling back to sysfs fallback for: vpu/vpu_fw_imx6q.bin coda 2040000.vpu: Direct firmware load for v4l-coda960-imx6q.bin failed with error -2
coda 2040000.vpu: Falling back to sysfs fallback for: v4l-coda960-imx6q.bin coda 2040000.vpu: firmware request failed

It seems that vpu directory is expected to be in "firmware" directory:
$(TARGET_DIR)/lib/firmware/vpu

Quoted 8 lines

see:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=8af7779f3cbc1f6720d15f00abc797493710d1ab

At least we have to create a simlink:
/lib/firmware/imx/vpu -> /lib/firmware/vpu

or set fw_path_para in the kernel cmdline:
firmware_class.path=/lib/firmware/imx/

I notice the same here on a imx53.

Then I tried to change the VPU path like this:

package/freescale-imx/firmware-imx/firmware-imx.mk +2 -2
@@ -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
Quoted 7 lines

,but the VPU firmware is still not found:

[    9.237801] coda 63ff4000.vpu: IRQ bit not found
[    9.291801] coda 63ff4000.vpu: Direct firmware load for
vpu_fw_imx53.bin failed with error -2
[    9.300646] coda 63ff4000.vpu: Falling back to sysfs fallback for:

vpu_fw_imx53.bin

There are several path supported (see the link above):

[CODA_IMX53] = {
.firmware = {
"vpu_fw_imx53.bin",

			"vpu/vpu_fw_imx53.bin",

"v4l-coda7541-imx53.bin"
},

So with your change, the first try fail using "/lib/firmware/vpu_fw_imx53.bin". But "/lib/firmware/vpu/vpu_fw_imx53.bin" succeed.

"firmware request failed" message should never appear in your dmesg log.

I believe there is a confusion between firmware (such vpu firmware) and imx sdma firmware that require to be installed to "/lib/firmware/imx" directory.

See:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/arch/arm/boot/dts/imx6qdl.dtsi?id=8af7779f3cbc1f6720d15f00abc797493710d1ab#n883

Best regards,
Romain

Quoted 18 lines

done
Saving random seed: [ 9.997216] random: dd: uninitialized urandom
read (512 bytes read)
OK
Starting network: OK

Welcome to Buildroot
buildroot login: root

# ls /lib/firmware/vpu/vpu_fw_imx53.bin
/lib/firmware/vpu/vpu_fw_imx53.bin
#

Any ideas?

Thanks,

Fabio Estevam

#10 lore raw

PATCH v2 1/8 package/freescale-imx/firmware-imx: bump version to 8.10

Hi All,

Quoted 7 lines

So with your change, the first try fail using "/lib/firmware/vpu_fw_imx53.bin". But "/lib/firmware/vpu/vpu_fw_imx53.bin" succeed.

"firmware request failed" message should never appear in your dmesg log.

I believe there is a confusion between firmware (such vpu firmware) and imx sdma firmware that require to be installed to "/lib/firmware/imx" directory.

Not really related to this discussion about vpu fw but I also faced an issue with an imx8mq board and the SDMA firmware.

# dmesg | grep sdma
[    0.178729] imx-sdma 302c0000.sdma: Direct firmware load for
imx/sdma/sdma-imx7d.bin failed with error -2
[    0.178763] imx-sdma 302c0000.sdma: Falling back to sysfs fallback
for: imx/sdma/sdma-imx7d.bin
[   60.381850] imx-sdma 302c0000.sdma: external firmware not found,
using ROM firmware
[   60.389889] imx-sdma 30bd0000.sdma: external firmware not found,
using ROM firmware
# ls /lib/firmware/imx/sdma/^C
# find / -name sdma-imx7d.bin
/lib/firmware/imx/sdma/sdma-imx7d.bin

Has anyone an idea what is going wrong?

Thank you

Signature · 1 line
Heiko
#11 lore raw

PATCH v2 1/8 package/freescale-imx/firmware-imx: bump version to 8.10

Hello Heiko,

Le 13/01/2021 ? 09:27, Heiko Thiery a ?crit?:

Quoted 10 lines

Hi All,

Quoted 7 lines

So with your change, the first try fail using "/lib/firmware/vpu_fw_imx53.bin". But "/lib/firmware/vpu/vpu_fw_imx53.bin" succeed.

"firmware request failed" message should never appear in your dmesg log.

I believe there is a confusion between firmware (such vpu firmware) and imx sdma firmware that require to be installed to "/lib/firmware/imx" directory.

Quoted 8 lines

Not really related to this discussion about vpu fw but I also faced an issue with an imx8mq board and the SDMA firmware.

# dmesg | grep sdma
[    0.178729] imx-sdma 302c0000.sdma: Direct firmware load for
imx/sdma/sdma-imx7d.bin failed with error -2
[    0.178763] imx-sdma 302c0000.sdma: Falling back to sysfs fallback
for: imx/sdma/sdma-imx7d.bin

based on the log timing, I would say that the rootfs wasn't mounted when the imx-sdma has been probed.

Try to compile the driver as a module, not bundled into the kernel image.

Best regards,
Romain

Quoted 12 lines
[   60.381850] imx-sdma 302c0000.sdma: external firmware not found,
using ROM firmware
[   60.389889] imx-sdma 30bd0000.sdma: external firmware not found,
using ROM firmware
# ls /lib/firmware/imx/sdma/^C
# find / -name sdma-imx7d.bin
/lib/firmware/imx/sdma/sdma-imx7d.bin

Has anyone an idea what is going wrong?

Thank you

#12 lore raw

PATCH v2 1/8 package/freescale-imx/firmware-imx: bump version to 8.10

Hi Romain,

Am Mi., 13. Jan. 2021 um 09:39 Uhr schrieb Romain Naour <[email protected]>:

Quoted 23 lines

Hello Heiko,

Le 13/01/2021 ? 09:27, Heiko Thiery a ?crit :

Quoted 10 lines

Hi All,

Quoted 7 lines

So with your change, the first try fail using "/lib/firmware/vpu_fw_imx53.bin". But "/lib/firmware/vpu/vpu_fw_imx53.bin" succeed.

"firmware request failed" message should never appear in your dmesg log.

I believe there is a confusion between firmware (such vpu firmware) and imx sdma firmware that require to be installed to "/lib/firmware/imx" directory.

Quoted 8 lines

Not really related to this discussion about vpu fw but I also faced an issue with an imx8mq board and the SDMA firmware.

# dmesg | grep sdma
[    0.178729] imx-sdma 302c0000.sdma: Direct firmware load for
imx/sdma/sdma-imx7d.bin failed with error -2
[    0.178763] imx-sdma 302c0000.sdma: Falling back to sysfs fallback
for: imx/sdma/sdma-imx7d.bin
Quoted 4 lines

based on the log timing, I would say that the rootfs wasn't mounted when the imx-sdma has been probed.

Try to compile the driver as a module, not bundled into the kernel image.

Then I misunderstand the mechanism. I thought it would be retried after 60 Seconds. I will try to compile it as a module and not builtin.

Thank you.

Signature · 1 line
Heiko
#13 lore raw

PATCH v2 1/8 package/freescale-imx/firmware-imx: bump version to 8.10

Hello Heiko,

Le 13/01/2021 ? 12:56, Heiko Thiery a ?crit?:

Quoted 26 lines

Hi Romain,

Am Mi., 13. Jan. 2021 um 09:39 Uhr schrieb Romain Naour <[email protected]>:

Quoted 23 lines

Hello Heiko,

Le 13/01/2021 ? 09:27, Heiko Thiery a ?crit :

Quoted 18 lines

Hi All,

Quoted 7 lines

So with your change, the first try fail using "/lib/firmware/vpu_fw_imx53.bin". But "/lib/firmware/vpu/vpu_fw_imx53.bin" succeed.

"firmware request failed" message should never appear in your dmesg log.

I believe there is a confusion between firmware (such vpu firmware) and imx sdma firmware that require to be installed to "/lib/firmware/imx" directory.

Not really related to this discussion about vpu fw but I also faced an issue with an imx8mq board and the SDMA firmware.

# dmesg | grep sdma
[    0.178729] imx-sdma 302c0000.sdma: Direct firmware load for
imx/sdma/sdma-imx7d.bin failed with error -2
[    0.178763] imx-sdma 302c0000.sdma: Falling back to sysfs fallback
for: imx/sdma/sdma-imx7d.bin
Quoted 8 lines
Quoted 4 lines

based on the log timing, I would say that the rootfs wasn't mounted when the imx-sdma has been probed.

Try to compile the driver as a module, not bundled into the kernel image.

Then I misunderstand the mechanism. I thought it would be retried after 60 Seconds. I will try to compile it as a module and not builtin.

For some reason it doesn't seems to try again...

It you want to compile the driver into the kernel, you may want to use CONFIG_EXTRA_FIRMWARE to add the firmware blob into the kernel image. But you have to be careful with the license.

Best regards,
Romain

Quoted 3 lines

Thank you.

#14 lore raw

PATCH v2 1/8 package/freescale-imx/firmware-imx: bump version to 8.10

In reply to Stephane Viau

Hi Stephane,

Le 05/01/2021 ? 16:24, Stephane Viau a ?crit?:

Quoted 5 lines

- Same version as NXP release 5.4.70-2.3.0
- EULA/COPYING: update to LA_OPT_NXP_Software_License v17

Still not related to this version bump but the sdma firmwares for imx[6,7,8] are provided by two packages: firmware-imx and linux-firmware

$ sha256sum ./firmware-imx-8.10/firmware/sdma/sdma-imx6q.bin
7790c161b7e013a9dbcbffb17cc5d4cb63d952949a505647e4679f02d04c4784
./firmware-imx-8.10/firmware/sdma/sdma-imx6q.bin
$ sha256sum  ./linux-firmware-20201022/imx/sdma/sdma-imx6q.bin
7790c161b7e013a9dbcbffb17cc5d4cb63d952949a505647e4679f02d04c4784
./linux-firmware-20201022/imx/sdma/sdma-imx6q.bin

We have two options: BR2_PACKAGE_FIRMWARE_IMX_SDMA_FW_NAME and BR2_PACKAGE_LINUX_FIRMWARE_IMX_SDMA

The only difference is that firmware-imx provide firmware for old imx cpus.

$ ls linux-firmware-20201022/imx/sdma/sdma-imx
sdma-imx6q.bin  sdma-imx7d.bin
$ ls firmware-imx-8.10/firmware/sdma/sdma-imx
sdma-imx25-to1.bin  sdma-imx31-to1.bin  sdma-imx31-to2.bin  sdma-imx35-to1.bin
sdma-imx35-to2.bin  sdma-imx51-to3.bin  sdma-imx53-to1.bin  sdma-imx6q.bin
sdma-imx7d.bin

Maybe we can keep one of firmware provider.

Best regards,
Romain

Quoted 35 lines

---
v2:
- Add "EULA/COPYING: update to LA_OPT_NXP_Software_License v17" in commit log (Gary)

---
 package/freescale-imx/firmware-imx/firmware-imx.hash | 6 +++---
 package/freescale-imx/firmware-imx/firmware-imx.mk   | 2 +-
 2 files changed, 4 insertions(+), 4 deletions(-)
package/freescale-imx/firmware-imx/firmware-imx.hash +3 -3
index 3230677d49..0a717d40f5 100644
@@ -1,4 +1,4 @@
 # Locally calculated
-sha256  a72f70fd2ecaa58800bb88ed672fddc322ab9843ee7777eb89b82016b0aa3614  firmware-imx-8.9.bin
-sha256  a39da2e94bd8b99eaac4325633854620ea3a55145259c3a7748c610a80714cfc  EULA
-sha256  69cbb76b3f10ac5a8c36f34df7bbdf50825815560c00a946fff2922365ef01a2  COPYING
+sha256  2b70f169d4065b2a7ac7a676afe24636128bd2dacc9f5230346758c3b146b2be  firmware-imx-8.10.bin
+sha256  72edc2072c86d93aa1993d15d4d19d96270af3749b0108995ad50c81d1461f52  EULA
+sha256  9c16421e7c702f56756650b8ac954d34556327e598a8666e6e8f4eb3a1aa95f1  COPYING
package/freescale-imx/firmware-imx/firmware-imx.mk +1 -1
index 7d1f42f1d8..b33ffb7ee8 100644
@@ -4,7 +4,7 @@
 #
 ################################################################################
 
-FIRMWARE_IMX_VERSION = 8.9
+FIRMWARE_IMX_VERSION = 8.10
 FIRMWARE_IMX_SITE = $(FREESCALE_IMX_SITE)
 FIRMWARE_IMX_SOURCE = firmware-imx-$(FIRMWARE_IMX_VERSION).bin
 
#15 lore raw

PATCH v2 1/8 package/freescale-imx/firmware-imx: bump version to 8.10

Quoted 2 lines

Hi Stephane,

Hi Romain,

Quoted 14 lines

Le 05/01/2021 ? 16:24, Stephane Viau a ?crit :

Quoted 5 lines

- Same version as NXP release 5.4.70-2.3.0
- EULA/COPYING: update to LA_OPT_NXP_Software_License v17

Still not related to this version bump but the sdma firmwares for imx[6,7,8] are provided by two packages: firmware-imx and linux-firmware

$ sha256sum ./firmware-imx-8.10/firmware/sdma/sdma-imx6q.bin
7790c161b7e013a9dbcbffb17cc5d4cb63d952949a505647e4679f02d04c4784
./firmware-imx-8.10/firmware/sdma/sdma-imx6q.bin
Quoted 6 lines
$ sha256sum  ./linux-firmware-20201022/imx/sdma/sdma-imx6q.bin
7790c161b7e013a9dbcbffb17cc5d4cb63d952949a505647e4679f02d04c4784
./linux-firmware-20201022/imx/sdma/sdma-imx6q.bin

We have two options: BR2_PACKAGE_FIRMWARE_IMX_SDMA_FW_NAME and BR2_PACKAGE_LINUX_FIRMWARE_IMX_SDMA

I don't know the whole history behind the presence of both options but what I know is that some effort has been put in over the last 6 months or so to clean up the package/freescale-imx/firmware-imx, including the logic behind "when to fetch the sdma firmware?" (BR2_PACKAGE_FIRMWARE_IMX_NEEDS_SDMA_FW).

Quoted 6 lines

The only difference is that firmware-imx provide firmware for old imx cpus.

$ ls linux-firmware-20201022/imx/sdma/sdma-imx
sdma-imx6q.bin  sdma-imx7d.bin
Quoted 6 lines
$ ls firmware-imx-8.10/firmware/sdma/sdma-imx
sdma-imx25-to1.bin  sdma-imx31-to1.bin  sdma-imx31-to2.bin  sdma-imx35-to1.bin
sdma-imx35-to2.bin  sdma-imx51-to3.bin  sdma-imx53-to1.bin  sdma-imx6q.bin
sdma-imx7d.bin

Maybe we can keep one of firmware provider.

If a choice must be made, I'd pick the former option rather than the latter... but that's just my opinion.

BR,
Stephane.

Quoted 3 lines

Best regards,
Romain

#16 lore raw

PATCH v2 1/8 package/freescale-imx/firmware-imx: bump version to 8.10

Hi Stephane,

Le 16/01/2021 ? 22:31, Stephane Viau (OSS) a ?crit?:

Quoted 23 lines
Quoted 2 lines

Hi Stephane,

Hi Romain,

Quoted 18 lines

Le 05/01/2021 ? 16:24, Stephane Viau a ?crit :

Quoted 5 lines

- Same version as NXP release 5.4.70-2.3.0
- EULA/COPYING: update to LA_OPT_NXP_Software_License v17

Still not related to this version bump but the sdma firmwares for imx[6,7,8] are provided by two packages: firmware-imx and linux-firmware

$ sha256sum ./firmware-imx-8.10/firmware/sdma/sdma-imx6q.bin
7790c161b7e013a9dbcbffb17cc5d4cb63d952949a505647e4679f02d04c4784
./firmware-imx-8.10/firmware/sdma/sdma-imx6q.bin
$ sha256sum  ./linux-firmware-20201022/imx/sdma/sdma-imx6q.bin
7790c161b7e013a9dbcbffb17cc5d4cb63d952949a505647e4679f02d04c4784
./linux-firmware-20201022/imx/sdma/sdma-imx6q.bin
Quoted 7 lines
Quoted 2 lines

We have two options: BR2_PACKAGE_FIRMWARE_IMX_SDMA_FW_NAME and BR2_PACKAGE_LINUX_FIRMWARE_IMX_SDMA

I don't know the whole history behind the presence of both options but what I know is that some effort has been put in over the last 6 months or so to clean up the package/freescale-imx/firmware-imx, including the logic behind "when to fetch the sdma firmware?" (BR2_PACKAGE_FIRMWARE_IMX_NEEDS_SDMA_FW).

BR2_PACKAGE_LINUX_FIRMWARE_IMX_SDMA has been added back in 2017:

https://git.buildroot.net/buildroot/commit/?id=b87eec6555dd716d051285d7314d55143578dd63

But indeed, the firmware-imx package install sdma firmware since the package has been added back in 2012:

https://git.buildroot.net/buildroot/commit/?id=22001201ded95850f0f9388f26333c077230b6c6

Quoted 12 lines
Quoted 12 lines

The only difference is that firmware-imx provide firmware for old imx cpus.

$ ls linux-firmware-20201022/imx/sdma/sdma-imx
sdma-imx6q.bin  sdma-imx7d.bin
$ ls firmware-imx-8.10/firmware/sdma/sdma-imx
sdma-imx25-to1.bin  sdma-imx31-to1.bin  sdma-imx31-to2.bin  sdma-imx35-to1.bin
sdma-imx35-to2.bin  sdma-imx51-to3.bin  sdma-imx53-to1.bin  sdma-imx6q.bin
sdma-imx7d.bin
Quoted 4 lines
Quoted 1 line

Maybe we can keep one of firmware provider.

If a choice must be made, I'd pick the former option rather than the latter... but that's just my opinion.

Fabio, do you have an opinion ?

It seems BR2_PACKAGE_LINUX_FIRMWARE_IMX_SDMA install the same firmware than the one provided by firmware-imx package. Also BR2_PACKAGE_LINUX_FIRMWARE_IMX_SDMA in not used by any in-tree defconfigs.

If you're ok, we should remove it.

Best regards,
Romain

Quoted 7 lines

BR,
Stephane.

Quoted 3 lines

Best regards,
Romain

reviewer
#17 lore raw

PATCH v2 1/8 package/freescale-imx/firmware-imx: bump version to 8.10

Hi Romain,

Quoted 7 lines · Romain Naour

Fabio, do you have an opinion ?

It seems BR2_PACKAGE_LINUX_FIRMWARE_IMX_SDMA install the same firmware than the one provided by firmware-imx package. Also BR2_PACKAGE_LINUX_FIRMWARE_IMX_SDMA in not used by any in-tree defconfigs.

If you're ok, we should remove it.

Yes, agree. Only having the firmware-imx package is enough.

Thanks

#18 lore raw

PATCH v2 2/8 package/freescale-imx/imx-sc-firmware: bump version to 1.7.0

In reply to Stephane Viau

- Same version as NXP release 5.4.70-2.3.0
- EULA/COPYING: update to LA_OPT_NXP_Software_License v17

---
v2:
- Add "EULA/COPYING: update to LA_OPT_NXP_Software_License v17" in commit log (Gary)

---
 package/freescale-imx/imx-sc-firmware/imx-sc-firmware.hash | 6 +++---
 package/freescale-imx/imx-sc-firmware/imx-sc-firmware.mk   | 2 +-
 2 files changed, 4 insertions(+), 4 deletions(-)
package/freescale-imx/imx-sc-firmware/imx-sc-firmware.hash +3 -3
index 630ccc842d..661a77de1a 100644
@@ -1,4 +1,4 @@
 # Locally calculated
-sha256  d3b04a49bcfdb5c7aa7e8f5ff89c040e9dfde0e8cb4b22bfb31f9cbb22a9d310  imx-sc-firmware-1.6.0.bin
-sha256  a39da2e94bd8b99eaac4325633854620ea3a55145259c3a7748c610a80714cfc  EULA
-sha256  69cbb76b3f10ac5a8c36f34df7bbdf50825815560c00a946fff2922365ef01a2  COPYING
+sha256  db4c414d405aea6f013946d109db198798f40f71bf0810b9b50c027ca252b4b7  imx-sc-firmware-1.7.0.bin
+sha256  72edc2072c86d93aa1993d15d4d19d96270af3749b0108995ad50c81d1461f52  EULA
+sha256  9c16421e7c702f56756650b8ac954d34556327e598a8666e6e8f4eb3a1aa95f1  COPYING
package/freescale-imx/imx-sc-firmware/imx-sc-firmware.mk +1 -1
index dab6130d3d..b05ca3c724 100644
@@ -4,7 +4,7 @@
 #
 ################################################################################
 
-IMX_SC_FIRMWARE_VERSION = 1.6.0
+IMX_SC_FIRMWARE_VERSION = 1.7.0
 IMX_SC_FIRMWARE_SITE = $(FREESCALE_IMX_SITE)
 IMX_SC_FIRMWARE_SOURCE = imx-sc-firmware-$(IMX_SC_FIRMWARE_VERSION).bin
 
Signature · 1 line
2.29.2
#19 lore raw

PATCH v2 3/8 package/freescale-imx/imx-seco: bump version to 3.7.4

In reply to Stephane Viau

- Same version as NXP release 5.4.70-2.3.0
- EULA/COPYING: update to LA_OPT_NXP_Software_License v17

---
v2:
- Add "EULA/COPYING: update to LA_OPT_NXP_Software_License v17" in commit log (Gary)

---
 package/freescale-imx/imx-seco/imx-seco.hash | 6 +++---
 package/freescale-imx/imx-seco/imx-seco.mk   | 2 +-
 2 files changed, 4 insertions(+), 4 deletions(-)
package/freescale-imx/imx-seco/imx-seco.hash +3 -3
index c8526d2b57..2e111c64d7 100644
@@ -1,4 +1,4 @@
 # Locally calculated
-sha256  b09f63139df6c4dfef3533570cd60b22eb4c48eed05f314268178e80b8de40fc  imx-seco-3.7.1.bin
-sha256  a39da2e94bd8b99eaac4325633854620ea3a55145259c3a7748c610a80714cfc  EULA
-sha256  69cbb76b3f10ac5a8c36f34df7bbdf50825815560c00a946fff2922365ef01a2  COPYING
+sha256  2ed8177e48c8e33f742b3a642805be56a5ef56df78b1b29e10518552154da2bc  imx-seco-3.7.4.bin
+sha256  72edc2072c86d93aa1993d15d4d19d96270af3749b0108995ad50c81d1461f52  EULA
+sha256  9c16421e7c702f56756650b8ac954d34556327e598a8666e6e8f4eb3a1aa95f1  COPYING
package/freescale-imx/imx-seco/imx-seco.mk +1 -1
index cc46ad7e5d..f7aaca7e4b 100644
@@ -4,7 +4,7 @@
 #
 ################################################################################
 
-IMX_SECO_VERSION = 3.7.1
+IMX_SECO_VERSION = 3.7.4
 IMX_SECO_SITE = $(FREESCALE_IMX_SITE)
 IMX_SECO_SOURCE = imx-seco-$(IMX_SECO_VERSION).bin
 
Signature · 1 line
2.29.2
#20 lore raw

PATCH v2 4/8 package/imx-mkimage: bump to version rel_imx_5.4.70_2.3.0

In reply to Stephane Viau

---
v2:
- Add "Reviewed-by" (Gary)

---
 package/imx-mkimage/imx-mkimage.hash | 2 +-
 package/imx-mkimage/imx-mkimage.mk   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
package/imx-mkimage/imx-mkimage.hash +1 -1
index e06706070d..4d3af3cd95 100644
@@ -1,3 +1,3 @@
 # Locally calculated
-sha256 19745a7b9d06a420e7574328de65e6f5f7e82c87beed926c8f0f6bd1512afbe6  imx-mkimage-rel_imx_5.4.47_2.2.0.tar.gz
+sha256 26175ee0634bc07efe7fa64e306f8241919ed9fbea92dfd8881ffd05c1783f5a  imx-mkimage-rel_imx_5.4.70_2.3.0.tar.gz
 sha256 231f7edcc7352d7734a96eef0b8030f77982678c516876fcb81e25b32d68564c  COPYING
package/imx-mkimage/imx-mkimage.mk +1 -1
index 51eb79e5f5..626e3d873f 100644
@@ -4,7 +4,7 @@
 #
 ################################################################################
 
-IMX_MKIMAGE_VERSION = rel_imx_5.4.47_2.2.0
+IMX_MKIMAGE_VERSION = rel_imx_5.4.70_2.3.0
 IMX_MKIMAGE_SITE = https://source.codeaurora.org/external/imx/imx-mkimage
 IMX_MKIMAGE_SITE_METHOD = git
 IMX_MKIMAGE_LICENSE = GPL-2.0+
Signature · 1 line
2.29.2
#21 lore raw

PATCH v2 5/8 configs/freescale_imx6*: bump BSP components to 5.4.70_2.3.0

In reply to Stephane Viau
[run-tested on i.MX6Q SabreSD, build-tested only for other configs]
---
 configs/freescale_imx6dlsabreauto_defconfig | 4 ++--
 configs/freescale_imx6dlsabresd_defconfig   | 4 ++--
 configs/freescale_imx6qsabreauto_defconfig  | 4 ++--
 configs/freescale_imx6qsabresd_defconfig    | 4 ++--
 configs/freescale_imx6sxsabresd_defconfig   | 4 ++--
 configs/freescale_imx6ullevk_defconfig      | 4 ++--
 6 files changed, 12 insertions(+), 12 deletions(-)
configs/freescale_imx6dlsabreauto_defconfig +2 -2
index 623a714533..443dc92fb6 100644
@@ -18,7 +18,7 @@ BR2_TARGET_GENERIC_GETTY_PORT="ttymxc3"
 BR2_LINUX_KERNEL=y
 BR2_LINUX_KERNEL_CUSTOM_GIT=y
 BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://source.codeaurora.org/external/imx/linux-imx.git"
-BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="rel_imx_5.4.47_2.2.0"
+BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="rel_imx_5.4.70_2.3.0"
 BR2_LINUX_KERNEL_DEFCONFIG="imx_v7"
 BR2_LINUX_KERNEL_DTS_SUPPORT=y
 BR2_LINUX_KERNEL_INTREE_DTS_NAME="imx6dl-sabreauto"
@@ -40,5 +40,5 @@ BR2_TARGET_UBOOT_BOARDNAME="mx6dlsabreauto"
 BR2_TARGET_UBOOT_FORMAT_IMX=y
 BR2_TARGET_UBOOT_CUSTOM_GIT=y
 BR2_TARGET_UBOOT_CUSTOM_REPO_URL="https://source.codeaurora.org/external/imx/uboot-imx.git"
-BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="rel_imx_5.4.47_2.2.0"
+BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="rel_imx_5.4.70_2.3.0"
 BR2_TARGET_UBOOT_NEEDS_DTC=y
configs/freescale_imx6dlsabresd_defconfig +2 -2
index 98adb6ebdb..488ceef468 100644
@@ -18,7 +18,7 @@ BR2_TARGET_GENERIC_GETTY_PORT="ttymxc0"
 BR2_LINUX_KERNEL=y
 BR2_LINUX_KERNEL_CUSTOM_GIT=y
 BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://source.codeaurora.org/external/imx/linux-imx.git"
-BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="rel_imx_5.4.47_2.2.0"
+BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="rel_imx_5.4.70_2.3.0"
 BR2_LINUX_KERNEL_DEFCONFIG="imx_v7"
 BR2_LINUX_KERNEL_DTS_SUPPORT=y
 BR2_LINUX_KERNEL_INTREE_DTS_NAME="imx6dl-sabresd"
@@ -39,5 +39,5 @@ BR2_TARGET_UBOOT_BOARDNAME="mx6dlsabresd"
 BR2_TARGET_UBOOT_FORMAT_IMX=y
 BR2_TARGET_UBOOT_CUSTOM_GIT=y
 BR2_TARGET_UBOOT_CUSTOM_REPO_URL="https://source.codeaurora.org/external/imx/uboot-imx.git"
-BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="rel_imx_5.4.47_2.2.0"
+BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="rel_imx_5.4.70_2.3.0"
 BR2_TARGET_UBOOT_NEEDS_DTC=y
configs/freescale_imx6qsabreauto_defconfig +2 -2
index 4c2a2410a2..1a0c96d52c 100644
@@ -18,7 +18,7 @@ BR2_TARGET_GENERIC_GETTY_PORT="ttymxc3"
 BR2_LINUX_KERNEL=y
 BR2_LINUX_KERNEL_CUSTOM_GIT=y
 BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://source.codeaurora.org/external/imx/linux-imx.git"
-BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="rel_imx_5.4.47_2.2.0"
+BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="rel_imx_5.4.70_2.3.0"
 BR2_LINUX_KERNEL_DEFCONFIG="imx_v7"
 BR2_LINUX_KERNEL_DTS_SUPPORT=y
 BR2_LINUX_KERNEL_INTREE_DTS_NAME="imx6q-sabreauto"
@@ -40,5 +40,5 @@ BR2_TARGET_UBOOT_BOARDNAME="mx6qsabreauto"
 BR2_TARGET_UBOOT_FORMAT_IMX=y
 BR2_TARGET_UBOOT_CUSTOM_GIT=y
 BR2_TARGET_UBOOT_CUSTOM_REPO_URL="https://source.codeaurora.org/external/imx/uboot-imx.git"
-BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="rel_imx_5.4.47_2.2.0"
+BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="rel_imx_5.4.70_2.3.0"
 BR2_TARGET_UBOOT_NEEDS_DTC=y
configs/freescale_imx6qsabresd_defconfig +2 -2
index 775082c0a5..19d7173300 100644
@@ -18,7 +18,7 @@ BR2_TARGET_GENERIC_GETTY_PORT="ttymxc0"
 BR2_LINUX_KERNEL=y
 BR2_LINUX_KERNEL_CUSTOM_GIT=y
 BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://source.codeaurora.org/external/imx/linux-imx.git"
-BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="rel_imx_5.4.47_2.2.0"
+BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="rel_imx_5.4.70_2.3.0"
 BR2_LINUX_KERNEL_DEFCONFIG="imx_v7"
 BR2_LINUX_KERNEL_DTS_SUPPORT=y
 BR2_LINUX_KERNEL_INTREE_DTS_NAME="imx6q-sabresd"
@@ -40,5 +40,5 @@ BR2_TARGET_UBOOT_BOARDNAME="mx6qsabresd"
 BR2_TARGET_UBOOT_FORMAT_IMX=y
 BR2_TARGET_UBOOT_CUSTOM_GIT=y
 BR2_TARGET_UBOOT_CUSTOM_REPO_URL="https://source.codeaurora.org/external/imx/uboot-imx.git"
-BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="rel_imx_5.4.47_2.2.0"
+BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="rel_imx_5.4.70_2.3.0"
 BR2_TARGET_UBOOT_NEEDS_DTC=y
configs/freescale_imx6sxsabresd_defconfig +2 -2
index bf7986701c..1628d7c5a5 100644
@@ -18,7 +18,7 @@ BR2_TARGET_GENERIC_GETTY_PORT="ttymxc0"
 BR2_LINUX_KERNEL=y
 BR2_LINUX_KERNEL_CUSTOM_GIT=y
 BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://source.codeaurora.org/external/imx/linux-imx.git"
-BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="rel_imx_5.4.47_2.2.0"
+BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="rel_imx_5.4.70_2.3.0"
 BR2_LINUX_KERNEL_DEFCONFIG="imx_v7"
 BR2_LINUX_KERNEL_DTS_SUPPORT=y
 BR2_LINUX_KERNEL_INTREE_DTS_NAME="imx6sx-sdb"
@@ -38,6 +38,6 @@ BR2_TARGET_UBOOT=y
 BR2_TARGET_UBOOT_BOARDNAME="mx6sxsabresd"
 BR2_TARGET_UBOOT_CUSTOM_GIT=y
 BR2_TARGET_UBOOT_CUSTOM_REPO_URL="https://source.codeaurora.org/external/imx/uboot-imx.git"
-BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="rel_imx_5.4.47_2.2.0"
+BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="rel_imx_5.4.70_2.3.0"
 BR2_TARGET_UBOOT_FORMAT_IMX=y
 BR2_TARGET_UBOOT_NEEDS_DTC=y
configs/freescale_imx6ullevk_defconfig +2 -2
index 39edc6f961..88d095d400 100644
@@ -6,7 +6,7 @@ BR2_ROOTFS_POST_IMAGE_SCRIPT="board/freescale/common/imx/post-image.sh"
 BR2_LINUX_KERNEL=y
 BR2_LINUX_KERNEL_CUSTOM_GIT=y
 BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://source.codeaurora.org/external/imx/linux-imx.git"
-BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="rel_imx_5.4.47_2.2.0"
+BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="rel_imx_5.4.70_2.3.0"
 BR2_LINUX_KERNEL_DEFCONFIG="imx_v7"
 BR2_LINUX_KERNEL_DTS_SUPPORT=y
 BR2_LINUX_KERNEL_INTREE_DTS_NAME="imx6ull-14x14-evk"
@@ -17,7 +17,7 @@ BR2_TARGET_UBOOT=y
 BR2_TARGET_UBOOT_BOARDNAME="mx6ull_14x14_evk"
 BR2_TARGET_UBOOT_CUSTOM_GIT=y
 BR2_TARGET_UBOOT_CUSTOM_REPO_URL="https://source.codeaurora.org/external/imx/uboot-imx.git"
-BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="rel_imx_5.4.47_2.2.0"
+BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="rel_imx_5.4.70_2.3.0"
 BR2_TARGET_UBOOT_NEEDS_DTC=y
 BR2_TARGET_UBOOT_FORMAT_IMX=y
 BR2_PACKAGE_HOST_DOSFSTOOLS=y
Signature · 1 line
2.29.2
#22 lore raw

PATCH v2 6/8 configs/freescale_imx7dsabresd: bump BSP components to 5.4.70_2.3.0

In reply to Stephane Viau
---
 configs/freescale_imx7dsabresd_defconfig | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
configs/freescale_imx7dsabresd_defconfig +2 -2
index 087bdb6346..a8b1df19ff 100644
@@ -12,7 +12,7 @@ BR2_TARGET_GENERIC_GETTY_PORT="ttymxc0"
 BR2_LINUX_KERNEL=y
 BR2_LINUX_KERNEL_CUSTOM_GIT=y
 BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://source.codeaurora.org/external/imx/linux-imx.git"
-BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="rel_imx_5.4.47_2.2.0"
+BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="rel_imx_5.4.70_2.3.0"
 BR2_LINUX_KERNEL_DEFCONFIG="imx_v7"
 BR2_LINUX_KERNEL_DTS_SUPPORT=y
 BR2_LINUX_KERNEL_INTREE_DTS_NAME="imx7d-sdb"
@@ -27,7 +27,7 @@ BR2_TARGET_UBOOT=y
 BR2_TARGET_UBOOT_BOARDNAME="mx7dsabresd"
 BR2_TARGET_UBOOT_CUSTOM_GIT=y
 BR2_TARGET_UBOOT_CUSTOM_REPO_URL="https://source.codeaurora.org/external/imx/uboot-imx.git"
-BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="rel_imx_5.4.47_2.2.0"
+BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="rel_imx_5.4.70_2.3.0"
 BR2_TARGET_UBOOT_FORMAT_IMX=y
 BR2_TARGET_UBOOT_NEEDS_DTC=y
 
Signature · 1 line
2.29.2
#23 lore raw

PATCH v2 7/8 configs/freescale_imx8m*: bump BSP components to 5.4.70_2.3.0

In reply to Stephane Viau

Bump ATF, U-Boot and Linux kernel to the NXP BSP 5.4.70_2.3.0 versions.

Note for configs/freescale_imx8mmevk:

On 5.4.70_2.3.0 the default "i.MX8MM LPDDR4 EVK RevB board" support is removed and replaced by "i.MX8MM LPDDR4 EVK with QCA WIFI revB board".

In case an older revB board is used, then the following step in U-Boot is needed:

=> setenv fdt_file imx8mm-evk-revb-qca-wifi.dtb => saveenv
=> reset

Build- and run-tested on:
o i.MX8MN DDR4 EVK
o i.MX8MQ EVK
Build-tested only for other configs.

---
 configs/freescale_imx8mmevk_defconfig | 8 ++++----
 configs/freescale_imx8mnevk_defconfig | 6 +++---
 configs/freescale_imx8mqevk_defconfig | 6 +++---
 3 files changed, 10 insertions(+), 10 deletions(-)
configs/freescale_imx8mmevk_defconfig +4 -4
index 353b327ab8..13117189e5 100644
@@ -7,10 +7,10 @@ BR2_ROOTFS_POST_SCRIPT_ARGS="${UBOOT_DIR}/arch/arm/dts/imx8mm-evk.dtb"
 BR2_LINUX_KERNEL=y
 BR2_LINUX_KERNEL_CUSTOM_GIT=y
 BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://source.codeaurora.org/external/imx/linux-imx"
-BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="rel_imx_5.4.47_2.2.0"
+BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="rel_imx_5.4.70_2.3.0"
 BR2_LINUX_KERNEL_DEFCONFIG="imx_v8"
 BR2_LINUX_KERNEL_DTS_SUPPORT=y
-BR2_LINUX_KERNEL_INTREE_DTS_NAME="freescale/imx8mm-evk freescale/imx8mm-evk-revb"
+BR2_LINUX_KERNEL_INTREE_DTS_NAME="freescale/imx8mm-evk freescale/imx8mm-evk-revb-qca-wifi"
 BR2_LINUX_KERNEL_NEEDS_HOST_OPENSSL=y
 BR2_PACKAGE_FREESCALE_IMX=y
 BR2_PACKAGE_FREESCALE_IMX_PLATFORM_IMX8MM=y
@@ -21,14 +21,14 @@ BR2_TARGET_ROOTFS_EXT2_SIZE="120M"
 BR2_TARGET_ARM_TRUSTED_FIRMWARE=y
 BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_GIT=y
 BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_URL="https://source.codeaurora.org/external/imx/imx-atf"
-BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_VERSION="rel_imx_5.4.47_2.2.0"
+BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_VERSION="rel_imx_5.4.70_2.3.0"
 BR2_TARGET_ARM_TRUSTED_FIRMWARE_PLATFORM="imx8mm"
 BR2_TARGET_ARM_TRUSTED_FIRMWARE_BL31=y
 BR2_TARGET_UBOOT=y
 BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
 BR2_TARGET_UBOOT_CUSTOM_GIT=y
 BR2_TARGET_UBOOT_CUSTOM_REPO_URL="https://source.codeaurora.org/external/imx/uboot-imx"
-BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="rel_imx_5.4.47_2.2.0"
+BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="rel_imx_5.4.70_2.3.0"
 BR2_TARGET_UBOOT_BOARD_DEFCONFIG="imx8mm_evk"
 BR2_TARGET_UBOOT_NEEDS_DTC=y
 BR2_TARGET_UBOOT_FORMAT_CUSTOM=y
configs/freescale_imx8mnevk_defconfig +3 -3
index f9ccd898dc..192f5d297e 100644
@@ -7,7 +7,7 @@ BR2_ROOTFS_POST_SCRIPT_ARGS="${UBOOT_DIR}/arch/arm/dts/imx8mn-ddr4-evk.dtb"
 BR2_LINUX_KERNEL=y
 BR2_LINUX_KERNEL_CUSTOM_GIT=y
 BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://source.codeaurora.org/external/imx/linux-imx"
-BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="rel_imx_5.4.47_2.2.0"
+BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="rel_imx_5.4.70_2.3.0"
 BR2_LINUX_KERNEL_DEFCONFIG="imx_v8"
 BR2_LINUX_KERNEL_DTS_SUPPORT=y
 BR2_LINUX_KERNEL_INTREE_DTS_NAME="freescale/imx8mn-ddr4-evk"
@@ -22,14 +22,14 @@ BR2_TARGET_ROOTFS_EXT2_SIZE="120M"
 BR2_TARGET_ARM_TRUSTED_FIRMWARE=y
 BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_GIT=y
 BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_URL="https://source.codeaurora.org/external/imx/imx-atf"
-BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_VERSION="rel_imx_5.4.47_2.2.0"
+BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_VERSION="rel_imx_5.4.70_2.3.0"
 BR2_TARGET_ARM_TRUSTED_FIRMWARE_PLATFORM="imx8mn"
 BR2_TARGET_ARM_TRUSTED_FIRMWARE_BL31=y
 BR2_TARGET_UBOOT=y
 BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
 BR2_TARGET_UBOOT_CUSTOM_GIT=y
 BR2_TARGET_UBOOT_CUSTOM_REPO_URL="https://source.codeaurora.org/external/imx/uboot-imx"
-BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="rel_imx_5.4.47_2.2.0"
+BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="rel_imx_5.4.70_2.3.0"
 BR2_TARGET_UBOOT_BOARD_DEFCONFIG="imx8mn_ddr4_evk"
 BR2_TARGET_UBOOT_NEEDS_DTC=y
 BR2_TARGET_UBOOT_FORMAT_CUSTOM=y
configs/freescale_imx8mqevk_defconfig +3 -3
index c369ca075c..d5d22dcf2b 100644
@@ -7,7 +7,7 @@ BR2_ROOTFS_POST_SCRIPT_ARGS="${UBOOT_DIR}/arch/arm/dts/imx8mq-evk.dtb"
 BR2_LINUX_KERNEL=y
 BR2_LINUX_KERNEL_CUSTOM_GIT=y
 BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://source.codeaurora.org/external/imx/linux-imx"
-BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="rel_imx_5.4.47_2.2.0"
+BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="rel_imx_5.4.70_2.3.0"
 BR2_LINUX_KERNEL_DEFCONFIG="imx_v8"
 BR2_LINUX_KERNEL_DTS_SUPPORT=y
 BR2_LINUX_KERNEL_INTREE_DTS_NAME="freescale/imx8mq-evk"
@@ -21,14 +21,14 @@ BR2_TARGET_ROOTFS_EXT2_SIZE="120M"
 BR2_TARGET_ARM_TRUSTED_FIRMWARE=y
 BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_GIT=y
 BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_URL="https://source.codeaurora.org/external/imx/imx-atf"
-BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_VERSION="rel_imx_5.4.47_2.2.0"
+BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_VERSION="rel_imx_5.4.70_2.3.0"
 BR2_TARGET_ARM_TRUSTED_FIRMWARE_PLATFORM="imx8mq"
 BR2_TARGET_ARM_TRUSTED_FIRMWARE_BL31=y
 BR2_TARGET_UBOOT=y
 BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
 BR2_TARGET_UBOOT_CUSTOM_GIT=y
 BR2_TARGET_UBOOT_CUSTOM_REPO_URL="https://source.codeaurora.org/external/imx/uboot-imx"
-BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="rel_imx_5.4.47_2.2.0"
+BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="rel_imx_5.4.70_2.3.0"
 BR2_TARGET_UBOOT_BOARD_DEFCONFIG="imx8mq_evk"
 BR2_TARGET_UBOOT_NEEDS_DTC=y
 BR2_TARGET_UBOOT_FORMAT_CUSTOM=y
Signature · 1 line
2.29.2
#24 lore raw

PATCH v2 8/8 configs/freescale_imx8*: bump BSP components to 5.4.70_2.3.0

In reply to Stephane Viau

Bump ATF, U-Boot and Linux kernel to the NXP BSP 5.4.70_2.3.0 versions.

Build- and run-tested on:
o i.MX8QM MEK
o i.MX8QXP MEK rev B0

---
 configs/freescale_imx8qmmek_defconfig  | 6 +++---
 configs/freescale_imx8qxpmek_defconfig | 6 +++---
 2 files changed, 6 insertions(+), 6 deletions(-)
configs/freescale_imx8qmmek_defconfig +3 -3
index 4241c4d33b..0342c0a206 100644
@@ -6,7 +6,7 @@ BR2_ROOTFS_POST_SCRIPT_ARGS="${UBOOT_DIR}/arch/arm/dts/fsl-imx8qm-mek.dtb"
 BR2_LINUX_KERNEL=y
 BR2_LINUX_KERNEL_CUSTOM_GIT=y
 BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://source.codeaurora.org/external/imx/linux-imx"
-BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="rel_imx_5.4.47_2.2.0"
+BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="rel_imx_5.4.70_2.3.0"
 BR2_LINUX_KERNEL_DEFCONFIG="imx_v8"
 BR2_LINUX_KERNEL_DTS_SUPPORT=y
 BR2_LINUX_KERNEL_INTREE_DTS_NAME="freescale/imx8qm-mek"
@@ -22,14 +22,14 @@ BR2_TARGET_ROOTFS_EXT2_SIZE="120M"
 BR2_TARGET_ARM_TRUSTED_FIRMWARE=y
 BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_GIT=y
 BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_URL="https://source.codeaurora.org/external/imx/imx-atf"
-BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_VERSION="rel_imx_5.4.47_2.2.0"
+BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_VERSION="rel_imx_5.4.70_2.3.0"
 BR2_TARGET_ARM_TRUSTED_FIRMWARE_PLATFORM="imx8qm"
 BR2_TARGET_ARM_TRUSTED_FIRMWARE_BL31=y
 BR2_TARGET_UBOOT=y
 BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
 BR2_TARGET_UBOOT_CUSTOM_GIT=y
 BR2_TARGET_UBOOT_CUSTOM_REPO_URL="https://source.codeaurora.org/external/imx/uboot-imx"
-BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="rel_imx_5.4.47_2.2.0"
+BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="rel_imx_5.4.70_2.3.0"
 BR2_TARGET_UBOOT_BOARD_DEFCONFIG="imx8qm_mek"
 BR2_TARGET_UBOOT_NEEDS_DTC=y
 BR2_PACKAGE_HOST_DOSFSTOOLS=y
configs/freescale_imx8qxpmek_defconfig +3 -3
index c57c38ca5f..e37a7553ad 100644
@@ -8,7 +8,7 @@ BR2_ROOTFS_POST_SCRIPT_ARGS="${UBOOT_DIR}/arch/arm/dts/fsl-imx8qxp-mek.dtb"
 BR2_LINUX_KERNEL=y
 BR2_LINUX_KERNEL_CUSTOM_GIT=y
 BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://source.codeaurora.org/external/imx/linux-imx"
-BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="rel_imx_5.4.47_2.2.0"
+BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="rel_imx_5.4.70_2.3.0"
 BR2_LINUX_KERNEL_DEFCONFIG="imx_v8"
 BR2_LINUX_KERNEL_DTS_SUPPORT=y
 BR2_LINUX_KERNEL_INTREE_DTS_NAME="freescale/imx8qxp-mek"
@@ -24,14 +24,14 @@ BR2_TARGET_ROOTFS_EXT2_SIZE="120M"
 BR2_TARGET_ARM_TRUSTED_FIRMWARE=y
 BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_GIT=y
 BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_URL="https://source.codeaurora.org/external/imx/imx-atf"
-BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_VERSION="rel_imx_5.4.47_2.2.0"
+BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_VERSION="rel_imx_5.4.70_2.3.0"
 BR2_TARGET_ARM_TRUSTED_FIRMWARE_PLATFORM="imx8qx"
 BR2_TARGET_ARM_TRUSTED_FIRMWARE_BL31=y
 BR2_TARGET_UBOOT=y
 BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
 BR2_TARGET_UBOOT_CUSTOM_GIT=y
 BR2_TARGET_UBOOT_CUSTOM_REPO_URL="https://source.codeaurora.org/external/imx/uboot-imx"
-BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="rel_imx_5.4.47_2.2.0"
+BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="rel_imx_5.4.70_2.3.0"
 BR2_TARGET_UBOOT_BOARD_DEFCONFIG="imx8qxp_mek"
 BR2_TARGET_UBOOT_NEEDS_DTC=y
 BR2_PACKAGE_HOST_DOSFSTOOLS=y
Signature · 1 line
2.29.2
#25 lore raw

v2 cover Bump NXP BSP components to 5.4.70_2.3.0

In reply to Stephane Viau
Quoted 9 lines · On Tue, 5 Jan 2021 16:24:12 +0100 Stephane Viau <[email protected]>…

Stephane Viau (8):
package/freescale-imx/firmware-imx: bump version to 8.10 package/freescale-imx/imx-sc-firmware: bump version to 1.7.0 package/freescale-imx/imx-seco: bump version to 3.7.4 package/imx-mkimage: bump to version rel_imx_5.4.70_2.3.0 configs/freescale_imx6*: bump BSP components to 5.4.70_2.3.0 configs/freescale_imx7dsabresd: bump BSP components to 5.4.70_2.3.0 configs/freescale_imx8m*: bump BSP components to 5.4.70_2.3.0 configs/freescale_imx8*: bump BSP components to 5.4.70_2.3.0

Series applied. Thanks!

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com