| Age | Commit message (Collapse) | Author |
|---|
|
Add OP-TEE support. Add optee to MACHINE_FEATURES to enable OP-TEE
in u-boot-imx. OP-TEE is currently not supported by u-boot-fslc.
Enable Broadcom 4339 and 43455 WiFi modules.
Add missing UBOOT_CONFIG options emmc, nand, and qspi1.
Drop redundant SERIAL_CONSOLES assignment.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
|
Add OP-TEE support. Add optee to MACHINE_FEATURES to enable OP-TEE
in u-boot-imx. OP-TEE is currently not supported by u-boot-fslc.
Enable Broadcom 4339 and 43455 WiFi modules.
Remove pci which is not supported by 6UL EVK.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
|
Add OP-TEE support. Add optee to MACHINE_FEATURES to enable OP-TEE
in u-boot-imx. OP-TEE is currently not supported by u-boot-fslc.
Enable Broadcom 4339 and 43455 WiFi modules.
Add PCIE EP device tree.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
|
Add OP-TEE support. Add optee to MACHINE_FEATURES to enable OP-TEE
in u-boot-imx. OP-TEE is currently not supported by u-boot-fslc.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
|
Add OP-TEE support. Add optee to MACHINE_FEATURES to enable OP-TEE
in u-boot-imx. OP-TEE is currently not supported by u-boot-fslc.
Enable Broadcom 4339 and 43455 WiFi modules.
Remove pci which is not supported by 6SLL EVK.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
|
Add OP-TEE support. Add optee to MACHINE_FEATURES to enable OP-TEE
in u-boot-imx. OP-TEE is currently not supported by u-boot-fslc.
Enable Broadcom 4339 and 43455 WiFi modules.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
|
The variable IMAGE_BOOTLOADER is not used since the move to wic.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
|
When `use-nxp-bsp` is active, several variables are missing default values and
contain only the additional values for `use-nxp-bsp`. Fix this by replacing
the override `_use-nxp-bsp_append` with `_append_use-nxp-bsp`.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
|
The DEFAULTTUNE and UBOOT_ENTRYPOINT are the same for all 8M, so
set them using the mx8m override.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
|
The use-*-bsp rework renamed use-fsl-bsp to use-nxp-bsp.
It also added to MACHINEOVERRIDES automatically, so fix the comment
as well.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
|
Signed-off-by: Gary Bisson <gary.bisson@boundarydevices.com>
|
|
That way all platforms are setup the same way.
Signed-off-by: Gary Bisson <gary.bisson@boundarydevices.com>
|
|
All patches were merged in upstream cryptodev-linux repository.
cryptodev recipes for qoriq in this layer used the same codes with
the ones in poky. Remove to avoid maintenance efforts.
Signed-off-by: Ting Liu <ting.liu@nxp.com>
|
|
Signed-off-by: Ting Liu <ting.liu@nxp.com>
|
|
NOTE: Multiple providers are available for u-boot-tools-native (u-boot-tools-native, u-boot-imx-tools-native)
Consider defining a PREFERRED_PROVIDER entry to match u-boot-tools-native
NOTE: Multiple providers are available for u-boot-mkimage-native (u-boot-imx-tools-native, u-boot-tools-native)
Consider defining a PREFERRED_PROVIDER entry to match u-boot-mkimage-native
NOTE: Multiple providers are available for runtime u-boot-mkimage (u-boot-imx-tools, u-boot-tools)
Consider defining a PREFERRED_RPROVIDER entry to match u-boot-mkimage
NOTE: Multiple providers are available for runtime nativesdk-u-boot-mkimage (nativesdk-u-boot-imx-tools, nativesdk-u-boot-tools)
Consider defining a PREFERRED_RPROVIDER entry to match nativesdk-u-boot-mkimage
Signed-off-by: Ting Liu <ting.liu@nxp.com>
|
|
lx2160aqds is board based on LX2162A processor.
The LX2162A (also known as LX2-Lite) processor squeezes the processing
capability of the popular LX2160A device into a package that is nearly one
quarter the size. It combines the low power of the 16nm FinFET process
technology and sixteen Arm Cortex-A72 cores with data path acceleration
optimized for L2/3 packet processing, security offload and robust traffic
management and quality of service.
More info:
https://www.nxp.com/products/processors-and-microcontrollers/arm-processors/layerscape-multicore-processors/layerscape-lx2162a-multicore-communications-processor:LX2162A
Signed-off-by: Ting Liu <ting.liu@nxp.com>
|
|
For now, the best alternative we have is to add the imx-boot to the
depends list based on the architecture. We bind it to use-mainline-bsp
so we avoid changing QoriQ machines.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Change-Id: I836015607b72dd6afbbb098925a789d4720460bd
|
|
We need to get mx8m out of the machine overrides to avoid adding NXP BSP
specific overrides in the system.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Change-Id: Ib99d5c6914c95cd18684a0e699da6679853f30b4
|
|
imx-boot is required to be provided as a dependency for mx8m machines in
order to provide a boot container, which WIC is expecting to include
into the final image.
Since the only dependency for WIC present in the layer now is targeting
mx8 machine and MACHINEOVERRIDES_EXTENDER_FILTER_OUT removes it when
use-mainline-bsp is set - it leaves no 'imx-boot' container in the path
of creating WIC file, and build for mx8m machines fails.
Append WKS_FILE_DEPENDS to include imx-boot for mx8m, as it is required
to be present regardless of the BSP flavor chosen.
Fixes: e2589ccb ("imx-base.inc: Avoid adding 'imx-boot' as dependency for all SoCs")
Signed-off-by: Andrey Zhizhikin <andrey.z@gmail.com>
|
|
The use-mainline-bsp cannot be used to add the 'imx-boot' on the
dependency chain as it breaks the other SoCs. The fix for this is still
to be decided but for now restore the old behavior.
Fixes: b93dcbeb (conf: machine: imx8m[m,p]: add support for fslc bsp)
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
imx-boot provides a boot container, which is required for mx8m family of
SOCs to execute a boot sequence.
Allow the imx-boot to generate boot container for Mini, Nano and Plus
SOCs by adding use-mainline-bsp to the list of compatible machines.
In order to accommodate new boot container generation model, former
SOC_TARGET variable has been renamed to IMX_BOOT_SOC_TARGET and should
be explicitly defined in the target machine recipes. This is done to
indicate that even if the mx8mm machine is finter out from
MACHINEOVERRIDES by extender filter - this recipe picks up a proper
target definition for boot container construction.
Default ATF binary image is also now based on ATF_PLATFORM, which is
explicitly defined in the machine configuration file.
Current support includes only Mini, Nano and Plus SOCs from i.MX8M
family, and additions of further machines would require the definition
of ATF_PLATFORM and IMX_BOOT_SOC_TARGET to be moved out from imx-boot
recipe to a machine configuration file.
Signed-off-by: Andrey Zhizhikin <andrey.z@gmail.com>
|
|
Since ATF is required for i.MX8M series to boot the SOC, allow it to be
built when use-mainline-bsp is set.
Move ATF build platform definition to target machine configuration
files, since MACHINEOVERRIDES extender filters out the override that is
used to identify it in the recipe. Therefore, for those mx8m machines
that are ready to be built with mainline BSP - ATF build platform is
explicitly defined in the machine config in order to be properly set for
ATF build.
Signed-off-by: Andrey Zhizhikin <andrey.z@gmail.com>
|
|
Add support for FSL Community BSP to imx8mmevk, imx8mpevk and imx8mnevk
machines and ease restriction for those machines to be built with
NXP-only BSP. FSL Community BSP allows those machines to pick up upstream
components in order to construct the image.
Bootloader provider is now selected to provide either u-boot-imx or
u-boot-fslc for mx8mm machines based on the BSP flavor selected.
WIC container is defined to accommodate ATF and option OP-TEE from NXP,
as it is required for mx8mm family to boot.
Signed-off-by: Andrey Zhizhikin <andrey.z@gmail.com>
|
|
Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
|
|
Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
|
|
Both SoC families use the same vpu firmware packaged into
firmware-imx-vpu-imx8.
Note that a package by the name firmware-imx-vpu-imx8-qxp does
not exist.
Compare with https://source.codeaurora.org/external/imx/meta-imx/tree/meta-bsp/conf/layer.conf?h=zeus-5.4.47-2.2.0#n70
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
|
When building for 6Q in a common build folder, the sysroots
used for opencv were actually for a previous 6SL build,
causing a build break.
Fix the build break by setting the opencv packaging properly
as SoC-specific.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
|
We need to install the SDMA firmware for all i.MX8M based SoCs so it can
properly enable the DMA support, this has been done for following SoC
families:
- mx8mm
- mx8mn
- mx8mp
- mx8mq
Reported-by: Brian Hutchinson <b.hutchman@gmail.com>
Change-Id: I047164568e659a532307fdedab31cdbb521fdfa1
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
Add machine definition file based in NXP release 5.4.24-2.1.0
Modify imx-base.inc machine file to add defines required to bring new
machine definition into the base.
Signed-off-by: Andrey Zhizhikin <andrey.z@gmail.com>
|
|
The tune-specific package architecture is sufficient, no need to
use the more specific SOC or MACHINE package architecture.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
|
Update all recipes to pull sources from imx_5.4.24_2.1.0 branch in NXP
upstream and update SRCREV to match release tags.
Update PREFERRED_VERSION of optee for mx8 to point to 3.7.0.imx.
Following notes are additions to the version update of recipes:
--------------------------
optee-os:
- Refresh gcc10 patch to resolve the fuzz during apply
- Drop python patch as it is already applied upstream
- Add new machines to the list
optee-client:
- Update CFLAGS patch to match 3.7.0 version
- Split ${B} from ${S}, this makes build more clear
optee-test:
- Remove do_compile task and substitute with OEMAKE
Signed-off-by: Andrey Zhizhikin <andrey.z@gmail.com>
|
|
Update all recipe PN to match the one from upstream.
Latest delivery from NXP has VPU firmware for imx27 in the package, so
enable it to be included in the image.
It also also lacks the VPU firmware for imx8qxp, so disable the package
for now until it is provided from NXP.
firmware-imx has been re-worked to provide a more unified mechanism for
installing firmware files into ${D} and package split is expalined in
the comments section.
NOTE: This update uses new EULA v11 from NXP.
Signed-off-by: Andrey Zhizhikin <andrey.z@gmail.com>
|
|
Drop patch appplied upstream, remove additional install step which is
handled by imx-boot recipe.
Update u-boot dtb names in machine description files, upstream U-Boot
from NXP has DTB files renamed.
Upgrade u-boot-imx-tools and u-boot-imx-mfgtool to 2020.04 as well to
match u-boot-imx recipe.
Signed-off-by: Andrey Zhizhikin <andrey.zhizhikin@leica-geosystems.com>
|
|
ptpd-qoriq is no longer used and supported, remove the recipe.
Signed-off-by: Ting Liu <ting.liu@nxp.com>
(cherry picked from commit 693fc486334c87a00c28cd68c2db5c1a41f709cf)
|
|
Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
|
|
The virtual/bootloader for this board used to be u-boot-imx which does
not include the board in COMPATIBLE_MACHINE any more, so the choice is
migrate to u-boot-fslc.
Signed-off-by: Daiane Angolini <daiane.angolini@nxp.com>
|
|
There are no rule to make both dtb any more.
Signed-off-by: Daiane Angolini <daiane.angolini@nxp.com>
|
|
The virtual/bootloader for this board used to be u-boot-imx which does
not include the board in COMPATIBLE_MACHINE any more, so the choice is
migrate to u-boot-fslc.
The error message:
ERROR: Nothing PROVIDES 'virtual/bootloader' (but /media/daiane/TRIFORCE/yocto/dunfell/sources/poky/meta/recipes-core/images/core-image-minimal.bb DEPENDS on or otherwise requires it)
u-boot-imx PROVIDES virtual/bootloader but was skipped: incompatible with machine imx6sxsabreauto (not in COMPATIBLE_MACHINE)
Signed-off-by: Daiane Angolini <daiane.angolini@nxp.com>
|
|
The variable is unused and thus we should drop it completely.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Change-Id: I3b2afe47c364dda6f928c93f75524bfec90a2131
|
|
The linux-imx does not offer fixes for security issues as well as new
toolchain tooling, as we maintain an alternative Linux flavor it make
sense to use it.
The kernel can still to be overridden on the machine or
distro definition, so preserving the flexibility.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Change-Id: I2378881cf9951f3dd85f758edf19af48185a50e8
|
|
This reverts commit c1b638305c1ebf5d05abc3b1a211e99710b795ab.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Change-Id: I3df2ae0f5113d3bb9bb9a09f92f57f65211f0fc5
|
|
Signed-off-by: Antonin Godard <agodard@witekio.com>
|
|
Remove openssl-qoriq from MACHINE_SOCARCH_FILTER since openssl is used from
OE-core with just some patches for QorIQ.
Signed-off-by: Jens Rehsack <sno@netbsd.org>
|
|
The Linux mainline 5.4 provide only the imx6ull-14x14-evk.dtb and all
others only are provided by the NXP-based Linux fork. We move them to
the NXP BSP specific setting.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
We should avoid overriding the U-Boot and Linux kernel to imx flavour as
we might use mainline or their forks; this fixes build errors when using
fslc distros as:
,----[ Build error ]
| ERROR: Nothing PROVIDES 'virtual/kernel'
| linux-fslc-lts-4.19 PROVIDES virtual/kernel but was skipped: PREFERRED_PROVIDER_virtual/kernel set to linux-imx, not linux-fslc-lts-4.19
| linux-fslc-imx PROVIDES virtual/kernel but was skipped: incompatible with machine imx6ullevk (not in COMPATIBLE_MACHINE)
| linux-qoriq PROVIDES virtual/kernel but was skipped: incompatible with machine imx6ullevk (not in COMPATIBLE_MACHINE)
| linux-fslc PROVIDES virtual/kernel but was skipped: PREFERRED_PROVIDER_virtual/kernel set to linux-imx, not linux-fslc
| linux-imx PROVIDES virtual/kernel but was skipped: incompatible with machine imx6ullevk (not in COMPATIBLE_MACHINE)
| linux-fslc-qoriq PROVIDES virtual/kernel but was skipped: incompatible with machine imx6ullevk (not in COMPATIBLE_MACHINE)
| linux-yocto-rt PROVIDES virtual/kernel but was skipped: incompatible with machine imx6ullevk (not in COMPATIBLE_MACHINE)
| linux-yocto-tiny PROVIDES virtual/kernel but was skipped: incompatible with machine imx6ullevk (not in COMPATIBLE_MACHINE)
| linux-yocto-dev PROVIDES virtual/kernel but was skipped: incompatible with machine imx6ullevk (not in COMPATIBLE_MACHINE)
| linux-yocto PROVIDES virtual/kernel but was skipped: incompatible with machine imx6ullevk (not in COMPATIBLE_MACHINE)
| linux-dummy PROVIDES virtual/kernel but was skipped: PREFERRED_PROVIDER_virtual/kernel set to linux-imx, not linux-dummy
| ERROR: Required build target 'core-image-minimal' has no buildable providers.
| Missing or unbuildable dependency chain was: ['core-image-minimal', 'virtual/kernel']
`----
Fixes: #432
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
Secure boot does not have DM mode support for PPC, and driver
related changes are not tested due to bandwidth limitation.
Remove secure-boot u-boot configs from the build list.
Signed-off-by: Ting Liu <ting.liu@nxp.com>
|
|
Avoid PREFERRED_PROVIDER_u-boot and PREFERRED_PROVIDER_virtual/bootloader
drift apart as good as it gets without creating circular dependencies.
Read: there in one primary definition (PREFERRED_PROVIDER_u-boot) and the
second specification is relying on the primary.
Signed-off-by: Jens Rehsack <sno@netbsd.org>
|
|
u-boot-fw-utils have been replace by libubootenv which has been finalized with
commit d15639a0a27393aa455adae113f4692c27367e89
Author: Otavio Salvador <otavio@ossystems.com.br>
Date: Thu Apr 2 11:19:34 2020 -0300
u-boot-qoriq-fw-utils: Drop recipe as libubootenv works as replacement
Now we are using libubootenv and dropped the u-boot-qoriq-fw-utils, we
need to move the configuration file to the main recipe.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Remove choosing a preferred provider, too.
Signed-off-by: Jens Rehsack <sno@netbsd.org>
|
|
Instead of maintaing 98% copy of OE-core recipe without being up-to-date
as good as possible, inject patches into OE-core recipe of openssl when
compiling for the right platform.
Signed-off-by: Jens Rehsack <sno@netbsd.org>
|
Tom Hochstein
Gary Bisson
Ting Liu
Otavio Salvador
Andrey Zhizhikin
Fabio Berton
Max Krummenacher
Andrey Zhizhikin
Daiane Angolini
antznin
Jens Rehsack