| Both sides previous revision Previous revision Next revision | Previous revision |
| panel_upgrade [2025/12/31 12:34] – [manifests/ directory (shortened)] rpjday | panel_upgrade [2025/12/31 13:41] (current) – [U-Boot] rpjday |
|---|
| ===== repo content (all of this under .repo directory) ===== | ===== repo content (all of this under .repo directory) ===== |
| |
| It appears that this build uses the "repo" tool to check out all of the necessary repositories; all of this represents the build from back in the "zeus" release days a few years ago. | It appears that this build uses the "repo" tool to check out all of the necessary repositories; all of this represents the build from back in the "zeus" release days a few years ago. The manifest files can be found [[https://github.com/nxp-imx/imx-manifest/tree/imx-linux-zeus|here]]. |
| |
| ==== manifest.xml ==== | ==== manifest.xml ==== |
| |
| ==== manifests/ directory (.xml files only) === | ==== manifests/ directory (.xml files only) === |
| | |
| | Just to see the variety of manifest files. |
| |
| <code> | <code> |
| ==== manifests/imx-5.4.3-1.0.0.xml ==== | ==== manifests/imx-5.4.3-1.0.0.xml ==== |
| |
| The manifest file that seems to have been used. | The manifest file that //seems// to have been used. |
| |
| <code> | <code> |
| ==== hello.txt ==== | ==== hello.txt ==== |
| |
| This file was clearly the saved output of a "bitbake -e" command for the build, so we can display both the preferred providers and preferred versions that would have been used for the build: | This file was clearly the saved output of a "bitbake -e" command for the build, so we can display both the preferred providers and preferred versions that would have been used for the build. Remember that this represents a "zeus"-related build from a few years ago. |
| |
| <code> | <code> |
| </code> | </code> |
| |
| [[https://github.com/ADLINK/meta-adlink-nxp/tree/zeus/conf/machine|Here]] is the relevant ADLINK NXP layer, which contains the machine definition of the "lec-imx6-1" shown in the next file that was used for this build back then. | [[https://github.com/ADLINK/meta-adlink-nxp/tree/zeus/conf/machine|Here]] is the relevant ADLINK NXP layer, which contains the machine definition of the "lec-imx6-1" shown in the next file that was used for this build back then. That machine definition does not exist in newer releases of that layer. |
| |
| === local.conf === | === local.conf === |
| ${@make_dtb_boot_files(d)} \ | ${@make_dtb_boot_files(d)} \ |
| </code> | </code> |
| | |
| | ===== The sources/ directory ===== |
| | |
| | Here are the relevant layers/subdirectories in the ''sources/'' directory checked out with the ''repo'' command (irrelevant stuff and proprietary layers deleted): |
| | |
| | <code> |
| | drwxrwxr-x 3 rpjday rpjday 4096 Apr 8 2024 base |
| | drwxrwxr-x 8 rpjday rpjday 4096 Apr 8 2024 meta-adlink-nxp |
| | drwxrwxr-x 5 rpjday rpjday 4096 Apr 8 2024 meta-adlink-sema |
| | drwxrwxr-x 7 rpjday rpjday 4096 Apr 8 2024 meta-browser |
| | drwxrwxr-x 22 rpjday rpjday 4096 Apr 8 2024 meta-freescale |
| | drwxrwxr-x 7 rpjday rpjday 4096 Apr 8 2024 meta-freescale-3rdparty |
| | drwxrwxr-x 6 rpjday rpjday 4096 Apr 8 2024 meta-freescale-distro |
| | drwxrwxr-x 6 rpjday rpjday 4096 Apr 8 2024 meta-imx |
| | drwxrwxr-x 4 rpjday rpjday 4096 May 2 2024 meta-installer |
| | drwxrwxr-x 13 rpjday rpjday 4096 Apr 8 2024 meta-openembedded |
| | drwxrwxr-x 12 rpjday rpjday 4096 Apr 8 2024 meta-qt5 |
| | drwxrwxr-x 9 rpjday rpjday 4096 Apr 8 2024 meta-rust |
| | drwxrwxr-x 5 rpjday rpjday 4096 Apr 8 2024 meta-timesys |
| | drwxrwxr-x 11 rpjday rpjday 4096 Apr 8 2024 poky |
| | </code> |
| | |
| | Notes on the above: |
| | |
| | * The "base" directory represents the https://github.com/Freescale/fsl-community-bsp-base checkout. |
| | * You can see all of the standard OE/YP, Arm, Freescale and ADLINK-related layers; I'm sure not all of those layers are necessary for what is being built. |
| | * I've deleted the panel-specific layers since they're not relevant to getting a solid core-image-minimal build on the panel. |
| | |
| | ===== U-Boot ===== |
| | |
| | I see nothing in that tarball that represents the U-Boot source that was used to build the currently-installed U-Boot. Here's everything U-Boot-related under the ''sources/'' directory, none of which seems to represent the version installed on the panel: |
| | |
| | <code> |
| | $ cd sources |
| | $ find . -name u-boot* |
| | ./meta-freescale/recipes-bsp/u-boot |
| | ./meta-freescale/recipes-bsp/u-boot/u-boot-fslc-common_2019.07.inc |
| | ./meta-freescale/recipes-bsp/u-boot/u-boot-fslc-fw-utils_2019.07.bb |
| | ./meta-freescale/recipes-bsp/u-boot/u-boot-fslc_2019.07.bb |
| | ./meta-freescale/recipes-bsp/u-boot/u-boot-qoriq-fw-utils_2019.04.bb |
| | ./meta-freescale/recipes-bsp/u-boot/u-boot-mfgtool.inc |
| | ./meta-freescale/recipes-bsp/u-boot/u-boot-qoriq_2019.04.bb |
| | ./meta-freescale/recipes-bsp/u-boot/u-boot-imx_2018.03.bb |
| | ./meta-freescale/recipes-bsp/u-boot/u-boot-fslc-mxsboot_2019.07.bb |
| | ./meta-freescale/recipes-bsp/u-boot/u-boot-imx-mfgtool_2018.03.bb |
| | ./meta-freescale/recipes-bsp/u-boot/u-boot-qoriq-common_2019.04.inc |
| | ./meta-add-files/recipes-add-files/add-files-1.0/files/u-boot_LEC-iMX6q-1G_7new.imx |
| | ./meta-add-files/recipes-add-files/add-files-1.0/files/u-boot_LEC-iMX6q-1G_7old.imx |
| | ./meta-add-files/recipes-add-files/add-files-1.0/files/u-boot_LEC-iMX6q-1G_7.imx |
| | ./meta-freescale-3rdparty/recipes-bsp/u-boot |
| | ./meta-freescale-3rdparty/recipes-bsp/u-boot/u-boot-script-gateworks-imx |
| | ./meta-freescale-3rdparty/recipes-bsp/u-boot/u-boot-congatec_2016.01.bb |
| | ./meta-freescale-3rdparty/recipes-bsp/u-boot/u-boot-toradex_2016.11.inc |
| | ./meta-freescale-3rdparty/recipes-bsp/u-boot/u-boot-boundary_2018.07.bb |
| | ./meta-freescale-3rdparty/recipes-bsp/u-boot/u-boot-karo_git.bb |
| | ./meta-freescale-3rdparty/recipes-bsp/u-boot/u-boot-compulab_2014.10.bb |
| | ./meta-freescale-3rdparty/recipes-bsp/u-boot/u-boot-toradex-fw-utils |
| | ./meta-freescale-3rdparty/recipes-bsp/u-boot/u-boot-boundary-common_2018.07.inc |
| | ./meta-freescale-3rdparty/recipes-bsp/u-boot/u-boot-digi_2017.03.bb |
| | ./meta-freescale-3rdparty/recipes-bsp/u-boot/u-boot-gateworks-imx_2015.04.bb |
| | ./meta-freescale-3rdparty/recipes-bsp/u-boot/u-boot-toradex_2016.11.bb |
| | ./meta-freescale-3rdparty/recipes-bsp/u-boot/u-boot-congatec |
| | ./meta-freescale-3rdparty/recipes-bsp/u-boot/u-boot-script-boundary_2018.07.bb |
| | ./meta-freescale-3rdparty/recipes-bsp/u-boot/u-boot-toradex-fw-utils_2016.11.bb |
| | ./meta-freescale-3rdparty/recipes-bsp/u-boot/u-boot-boundary-fw-utils |
| | ./meta-freescale-3rdparty/recipes-bsp/u-boot/u-boot-boundary-fw-utils_2018.07.bb |
| | ./meta-freescale-3rdparty/recipes-bsp/u-boot/u-boot-script-gateworks-imx.bb |
| | ./meta-freescale-3rdparty/recipes-bsp/u-boot/u-boot-timesys_2011.12.bb |
| | ./meta-freescale-3rdparty/recipes-bsp/u-boot/u-boot-digi |
| | ./meta-freescale-3rdparty/recipes-bsp/u-boot/u-boot-fslc_%.bbappend |
| | ./meta-freescale-3rdparty/recipes-bsp/u-boot/u-boot-variscite_2017.03.bb |
| | ./meta-imx/meta-bsp/recipes-bsp/u-boot |
| | ./meta-imx/meta-bsp/recipes-bsp/u-boot/u-boot-tools_%.bbappend |
| | ./meta-imx/meta-bsp/recipes-bsp/u-boot/u-boot.inc |
| | ./meta-imx/meta-bsp/recipes-bsp/u-boot/u-boot-imx_2019.04.bb |
| | ./meta-imx/meta-bsp/recipes-bsp/u-boot/u-boot-common.inc |
| | ./meta-imx/meta-bsp/recipes-bsp/u-boot/u-boot-imx-mfgtool_2019.04.bb |
| | ./poky/meta/recipes-bsp/u-boot |
| | ./poky/meta/recipes-bsp/u-boot/u-boot_2019.07.bb |
| | ./poky/meta/recipes-bsp/u-boot/u-boot.inc |
| | ./poky/meta/recipes-bsp/u-boot/u-boot-tools_2019.07.bb |
| | ./poky/meta/recipes-bsp/u-boot/u-boot-common.inc |
| | ./poky/meta/recipes-bsp/u-boot/u-boot-fw-utils_2019.07.bb |
| | </code> |
| | |
| | The closest are the image files under the ''meta-add-files/'' layer, which appear to be flashable U-Boot images, but there is no record as to how they were built. |