board/mx6cubox: Switch to extlinux.conf
PATCH 1/1 board/mx6cubox: Switch to extlinux.conf
Currently mx6cubox uses a custom boot.scr.txt script and custom image generation scripts: genimage.cfg, post-build.sh and post-image.sh.
Switch to using the more standard extlinux.conf solution and remove the custom scripts in favor of the standard board/freescale/common/imx/post-image.sh one.
---
Hi Francois and Baruch,
I don't have access to mx6cubox. Please test this
patch if you have a chance.
Is it safe to apply the U-Boot patch that changes the mmc device for all cubox/hummingboard variants?
If it is OK, then I will send it to U-Boot upstream.
Thanks
board/solidrun/mx6cubox/boot.scr.txt | 7 ----- board/solidrun/mx6cubox/genimage.cfg | 29 ------------------- ...xi-Fix-the-mmc-device-for-the-rootfs.patch | 29 +++++++++++++++++++ board/solidrun/mx6cubox/post-build.sh | 8 ----- board/solidrun/mx6cubox/post-image.sh | 14 --------- .../boot/extlinux/extlinux.conf | 4 +++ configs/mx6cubox_defconfig | 5 ++-- 7 files changed, 36 insertions(+), 60 deletions(-) delete mode 100644 board/solidrun/mx6cubox/boot.scr.txt delete mode 100644 board/solidrun/mx6cubox/genimage.cfg create mode 100644 board/solidrun/mx6cubox/patches/uboot/0001-mx6cuboxi-Fix-the-mmc-device-for-the-rootfs.patch delete mode 100755 board/solidrun/mx6cubox/post-build.sh delete mode 100755 board/solidrun/mx6cubox/post-image.sh create mode 100644 board/solidrun/mx6cubox/rootfs_overlay/boot/extlinux/extlinux.conf
board/solidrun/mx6cubox/boot.scr.txt deleted +0 -7
@@ -1,7 +0,0 @@ -setenv finduuid "part uuid mmc 1:1 uuid" -run finduuid -run findfdt -setenv bootargs "console=ttymxc0,115200 root=PARTUUID=${uuid} rootwait rootfstype=ext4" -load mmc 1:1 ${fdt_addr} boot/${fdtfile} -load mmc 1:1 ${loadaddr} boot/zImage -bootz ${loadaddr} - ${fdt_addr}
board/solidrun/mx6cubox/genimage.cfg deleted +0 -29
@@ -1,29 +0,0 @@ -# Minimal SD card image for the MX6 Cubox/Hummingboard -# -# U-Boot SPL and u-boot.img are flashed in the first 1MB raw partition. -# A single root filesystem partition is used (Ext4 in this case). -# - -image sdcard.img { - hdimage { - } - - partition spl { - in-partition-table = "no" - image = "SPL" - offset = 1K - } - - partition u-boot { - in-partition-table = "no" - image = "u-boot.img" - offset = 69K - } - - partition rootfs { - partition-type = 0x83 - image = "rootfs.ext4" - offset = 1M - size = 512M - } -}
board/solidrun/mx6cubox/patches/uboot/0001-mx6cuboxi-Fix-the-mmc-device-for-the-rootfs.patch new file +29 -0
@@ -0,0 +1,29 @@ +From 96db7c072b96f9b7a1d9a986eff20353f7459004 Mon Sep 17 00:00:00 2001 +From: Fabio Estevam <[email protected]> +Date: Sun, 18 Jul 2021 19:08:36 -0300 +Subject: [PATCH] mx6cuboxi: Fix the mmc device for the rootfs + +After the comversion to DM_MMC, the rootfs is mmc 1, so +adjust it accordingly. + +Signed-off-by: Fabio Estevam <[email protected]> +--- + include/configs/mx6cuboxi.h | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/include/configs/mx6cuboxi.h b/include/configs/mx6cuboxi.h +index 55717c77ab38..1a06f29b8c17 100644 +--- a/include/configs/mx6cuboxi.h ++++ b/include/configs/mx6cuboxi.h +@@ -57,7 +57,7 @@ + "console=" CONSOLE_DEV ",115200\0" \ + "bootm_size=0x10000000\0" \ + "mmcdev=" __stringify(CONFIG_SYS_MMC_ENV_DEV) "\0" \ +- "finduuid=part uuid mmc 0:1 uuid\0" \ ++ "finduuid=part uuid mmc 1:1 uuid\0" \ + "update_sd_firmware=" \ + "if test ${ip_dyn} = yes; then " \ + "setenv get_cmd dhcp; " \ +-- +2.25.1 +
board/solidrun/mx6cubox/post-build.sh deleted +0 -8
@@ -1,8 +0,0 @@ -#!/bin/sh - -BOARD_DIR="$(dirname $0)" - -install -d -m 755 $TARGET_DIR/boot - -$HOST_DIR/bin/mkimage -A arm -O linux -T script -C none \ - -n "boot script" -d $BOARD_DIR/boot.scr.txt $TARGET_DIR/boot/boot.scr
board/solidrun/mx6cubox/post-image.sh deleted +0 -14
@@ -1,14 +0,0 @@ -#!/usr/bin/env bash - -BOARD_DIR="$(dirname $0)" -GENIMAGE_CFG="${BOARD_DIR}/genimage.cfg" -GENIMAGE_TMP="${BUILD_DIR}/genimage.tmp" - -rm -rf "${GENIMAGE_TMP}" - -genimage \ - --rootpath "${TARGET_DIR}" \ - --tmppath "${GENIMAGE_TMP}" \ - --inputpath "${BINARIES_DIR}" \ - --outputpath "${BINARIES_DIR}" \ - --config "${GENIMAGE_CFG}"
board/solidrun/mx6cubox/rootfs_overlay/boot/extlinux/extlinux.conf new file +4 -0
@@ -0,0 +1,4 @@ +Label imx6qdl-cubox Buildroot + kernel ../zImage + fdtdir ../ + append root=PARTUUID=${uuid} rootwait rw console=${console},${baudrate}
configs/mx6cubox_defconfig +3 -2
@@ -11,8 +11,9 @@ BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_5_10=y # System configuration BR2_TARGET_GENERIC_GETTY_PORT="ttymxc0" -BR2_ROOTFS_POST_BUILD_SCRIPT="board/solidrun/mx6cubox/post-build.sh" -BR2_ROOTFS_POST_IMAGE_SCRIPT="board/solidrun/mx6cubox/post-image.sh" +BR2_ROOTFS_OVERLAY="board/solidrun/mx6cubox/rootfs_overlay" +BR2_ROOTFS_POST_IMAGE_SCRIPT="board/freescale/common/imx/post-image.sh" +BR2_GLOBAL_PATCH_DIR="board/solidrun/mx6cubox/patches" # Kernel BR2_LINUX_KERNEL=y
Signature · 1 line
2.25.1
PATCH 1/1 board/mx6cubox: Switch to extlinux.conf
Le lun. 19 juil. 2021 ? 00:25, Fabio Estevam <[email protected]> a ?crit :
Quoted 8 lines
Currently mx6cubox uses a custom boot.scr.txt script and custom image generation scripts: genimage.cfg,
post-build.shandpost-image.sh.Switch to using the more standard extlinux.conf solution and remove the custom scripts in favor of the standard
board/freescale/common/imx/post-image.shone.
Quoted 8 lines
Signed-off-by Fabio Estevam <[email protected]>---
Hi Francois and Baruch,I don't have access to mx6cubox. Please test this patch if you have a chance.
Hello Fabio,
with this new version, the boot is OK,
but there still an issue with the console variable:
# cat /proc/cmdline root=PARTUUID=00000000-01 rootwait rw console=ttymxc0,115200,115200
Quoted 6 lines
Is it safe to apply the U-Boot patch that changes the mmc device for all cubox/hummingboard variants?
If it is OK, then I will send it to U-Boot upstream.
I think that the patch must be upstreamed.
Fran?ois
Quoted 17 lines
Thanks
board/solidrun/mx6cubox/boot.scr.txt | 7 ----- board/solidrun/mx6cubox/genimage.cfg | 29 ------------------- ...xi-Fix-the-mmc-device-for-the-rootfs.patch | 29 +++++++++++++++++++ board/solidrun/mx6cubox/post-build.sh | 8 ----- board/solidrun/mx6cubox/post-image.sh | 14 --------- .../boot/extlinux/extlinux.conf | 4 +++ configs/mx6cubox_defconfig | 5 ++-- 7 files changed, 36 insertions(+), 60 deletions(-) delete mode 100644 board/solidrun/mx6cubox/boot.scr.txt delete mode 100644 board/solidrun/mx6cubox/genimage.cfg create mode 100644 board/solidrun/mx6cubox/patches/uboot/0001-mx6cuboxi-Fix-the-mmc-device-for-the-rootfs.patch delete mode 100755 board/solidrun/mx6cubox/post-build.sh delete mode 100755 board/solidrun/mx6cubox/post-image.sh create mode 100644
Quoted 5 lines
board/solidrun/mx6cubox/rootfs_overlay/boot/extlinux/extlinux.conf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20210719/e72a17d4/attachment-0001.html>
PATCH 1/1 board/mx6cubox: Switch to extlinux.conf
Hi Fran?ois,
Quoted 3 lines · Fran?ois Perrad
Hello Fabio,
with this new version, the boot is OK,
Thanks for testing.
Quoted 3 lines
but there still an issue with the console variable:
# cat /proc/cmdline root=PARTUUID=00000000-01 rootwait rw console=ttymxc0,115200,115200
Yes, I will fix this issue in mainline U-Boot too.
Quoted 7 lines
Quoted 5 lines
Is it safe to apply the U-Boot patch that changes the mmc device for all cubox/hummingboard variants?
If it is OK, then I will send it to U-Boot upstream.
I think that the patch must be upstreamed.
I will upstream it.
Thanks,
Fabio Estevam