linux-imx.inc is using kernel-yocto class and it's necessary to set
LINUX_VERSION as shown in meta-freescale commit
c7e23876b199e2cfbc2aef6bf192ef50e665b1c5
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
We need to support both mainline and NXP BSP support, to allow that we
need:
- split generic and NXP BSP specific device trees
- avoid setting the default Linux kernel if we use mainline BSP
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
We need to support both mainline and NXP BSP support, to allow that we
need:
- split generic and NXP BSP specific device trees
- avoid setting the default Linux kernel if we use mainline BSP
This was applied for:
- colibri-imx7-emmc
- colibri-imx7-nand
Fixes: #78
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
This commit merges tag 'v5.4.41' into v5.4-ktn and apply the following
commits on top of it:
- 807a88195d767 ARM: imx: Fix boot crash if ocotp is not found
- 6c19e5d432b17 ARM: imx: Correct ocotp id for serial number support of i.MX6ULL/ULZ SoCs
- 0399822a7ccd6 soc: imx-scu: Using existing serial_number instead of UID
- f74ed0a5bfb86 ARM: imx: Add serial number support for i.MX6/7 SoCs
- d33c491a73198 ARM: dts: imx6ul-kontron-n6310-s: Move common nodes to a separate file
Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
This enables few extra options for the default configuration. It
enables:
- BOOTCOUNT_LIMIT
- BOOTCOUNT_ENV
- CMD_FS_UUID
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
This adds support for Kontron N63XX/N64XX SoM based boards and provides
following components:
- imx6ul-kontron machine definition
- u-boot-kontron recipe
- linux-kontron recipe
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
linux-imx.inc now inherits kernel-yocto class, so LINUX_VERSION must be
defined and also define KBUILD_DEFCONFIG to inform the class to use
boundary source tree defconfig.
Signed-off-by: Chris Dimich <Chris.Dimich@boundarydevices.com>
linux-imx.inc is using kernel-yocto class and it's necessary to set
LINUX_VERSION as shown in meta-freescale commit
c7e23876b199e2cfbc2aef6bf192ef50e665b1c5
Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
Use UBOOT_CONFIG instead of UBOOT_MACHINE, as per matches imx8mnevk.
Define IMAGE_BOOTLOADER and IMXBOOT_TARGETS as per imx8mnevk.
Define DDR_FIRMWARE_NAME as per imx8mnevk.
Signed-off-by: Chris Dimich <Chris.Dimich@boundarydevices.com>
Use UBOOT_CONFIG instead of UBOOT_MACHINE, as per imx8mmevk.
Define IMAGE_BOOTLOADER and IMXBOOT_TARGETS as per imx8mmevk.
Define DDR_FIRMWARE_NAME as per imx8mmevk.
Signed-off-by: Chris Dimich <Chris.Dimich@boundarydevices.com>
Add custom imx-atf applicable only to Nitrogen8m, Nitrogen8mm and
Nitrogen8mn, which pulls from Boundary's imx-atf. This is done because
meta-freescale imx-atf_2.0 sets the RDC so that UART4 is only accessible
by M4 core.
Signed-off-by: Chris Dimich <Chris.Dimich@boundarydevices.com>
Use UBOOT_CONFIG instead of UBOOT_MACHINE, as per imx8mqevk.
Define IMAGE_BOOTLOADER and IMXBOOT_TARGETS as per imx8mqevk.
Define DDR_FIRMWARE_NAME as per imx8mqevk.
Signed-off-by: Chris Dimich <Chris.Dimich@boundarydevices.com>
This fixes the following build error:
> Error, the PACKAGE_ARCHS variable (all any noarch ${PACKAGE_EXTRA_ARCHS_tune-cortexa53-crypto} nitrogen8m) for DEFAULTTUNE (cortexa53-crypto) does not contain TUNE_PKGARCH (${@bb.utils.contains('TUNE_FEATURES', 'aarch64', 'aarch64', '${ARMPKGARCH_tune-cortexa53-crypto}' ,d)}).Toolchain tunings invalid:
> Tuning 'cortexa53-crypto' has no defined features, and cannot be used.
Signed-off-by: Carlos Rafael Giani <crg7475@mailbox.org>
We now choose the BSP in a generic way and this commit changes the
machines to use the new mechanism setting it to mainline one.
Following changes are changed:
- imx6qdl-pico
- imx6ul-pico
- imx7d-pico
- imx7s-warp
- wandboard
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
The script is not required as libubootenv handles the unlock
automatically, so we can drop it now.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Now we are using libubootenv and dropped the u-boot-toradex-fw-utils, we
need to move the configuration file to the main recipe.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Now we are using libubootenv and dropped the u-boot-boundary-fw-utils,
we need to move the configuration file to the main recipe.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
The recipe seems abandoned as their U-Boot is not update for ages, so we
are dropping it for now. If desired, it can be reverted once updated.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
After discussing this in OE-Core we are renaming it so it follows same
naming pattern as u-boot-default-env.
Fixes: 80be160 (u-boot-script-toradex: Set virtual/bootscript as provider)
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
