Skip to contentSkip to conversation

configs/freescale_imx8mqevk: bump BSP components to 4.14.98_2.0.0

PATCH New Julien Olivain 3 participants 4 messages Dec 3, 2019 – Dec 8, 2019 Arm i.MX and Layerscape

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 configs/freescale_imx8mqevk: bump BSP components to 4.14.98_2.0.0

Update Kernel, U-Boot and ATF to NXP BSP version rel_imx_4.14.98_2.0.0_ga

---
 configs/freescale_imx8mqevk_defconfig | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
configs/freescale_imx8mqevk_defconfig +3 -3
index 7e96ee7fc0..7989b60570 100644
@@ -7,7 +7,7 @@ BR2_ROOTFS_POST_SCRIPT_ARGS="${UBOOT_DIR}/arch/arm/dts/fsl-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_4.14.78_1.0.0_ga"
+BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="rel_imx_4.14.98_2.0.0_ga"
 BR2_LINUX_KERNEL_USE_ARCH_DEFAULT_CONFIG=y
 BR2_LINUX_KERNEL_DTS_SUPPORT=y
 BR2_LINUX_KERNEL_INTREE_DTS_NAME="freescale/fsl-imx8mq-evk"
@@ -20,14 +20,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_4.14.78_1.0.0_ga"
+BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_REPO_VERSION="rel_imx_4.14.98_2.0.0_ga"
 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_4.14.78_1.0.0_ga"
+BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="rel_imx_4.14.98_2.0.0_ga"
 BR2_TARGET_UBOOT_BOARD_DEFCONFIG="imx8mq_evk"
 BR2_TARGET_UBOOT_NEEDS_DTC=y
 BR2_TARGET_UBOOT_FORMAT_IMX=y
Signature · 1 line
2.23.0
reviewer
#1 lore raw

PATCH 1/1 configs/freescale_imx8mqevk: bump BSP components to 4.14.98_2.0.0

Hi Julien,

Quoted 2 lines · Julien Olivain

Update Kernel, U-Boot and ATF to NXP BSP version rel_imx_4.14.98_2.0.0_ga

What about switching to imx_4.19.35_1.1.0 instead?

Thanks

#2 lore raw

PATCH 1/1 configs/freescale_imx8mqevk: bump BSP components to 4.14.98_2.0.0

Hi Fabio,

Quoted 8 lines · Fabio Estevam

Hi Julien,

Quoted 3 lines · Julien Olivain

Update Kernel, U-Boot and ATF to NXP BSP version
rel_imx_4.14.98_2.0.0_ga

What about switching to imx_4.19.35_1.1.0 instead?

Some packages, like imx-gpu-viv are linked to the i.MX uboot/kernel/atf versions. For example i.MX BSP 4.14.78-1.0.0 uses imx-gpu-viv-6.2.4.p2.3,
but 4.19.35-1.1.0 uses imx-gpu-viv-6.4.0.p1.0, ... (One could eventually workaround this by using kernel-module-imx-gpu-viv, though). This is also
probably the case for other i.MX packages like imx-sc-firmware (with SC RPC API
version), and firmware-imx, and maybe others...

On the other hand, some other board vendors are providing their own BSPs derived from older NXP BSPs (e.g. TechNexion latest BSP is still based on
4.14.98_2.0.0). So updating EVK board to 4.19.35_1.1.0 would probably require
an imx-gpu-viv update too, but would also probably break the TechNexion PicoPi
8M.

This means that, some of the i.MX defconfigs needs to be aligned altogether,
with those packages. My intent was to not update beyond the latest TechNexion
BSP version.

Maybe the correct long-term solution would be to add a "Custom Version" option
in KConfig, for those packages with kernel/uboot/atf dependencies?

Best regards,

Julien.

#3 lore raw

PATCH 1/1 configs/freescale_imx8mqevk: bump BSP components to 4.14.98_2.0.0

In reply to Julien Olivain
Quoted 6 lines · On Tue, 3 Dec 2019 21:38:05 +0100 Julien Olivain <[email protected]> wrote:

Update Kernel, U-Boot and ATF to NXP BSP version rel_imx_4.14.98_2.0.0_ga

---
 configs/freescale_imx8mqevk_defconfig | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

Applied to master, thanks.

Fabio: I saw your comment about bumping to 4.19. It obviously makes sense to upgrade to 4.19 when possible, but since bumping to a slightly newer 4.14 also makes sense on its own, I've applied Julien's patch. But of course, bumping to 4.19 needs to be done at some point in the future.

Thomas

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