| Age | Commit message (Collapse) | Author |
|---|
|
Fixes: 776932e1 ("Rework the u-boot-fslc and u-boot-imx settings logic")
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
For eventual use of u-boot-fslc as mfgtool flavor, this will need to be
provided as an extra UBOOT_CONFIG thus reusing same provider. This fix
some build errors with external layers.
Fixes: 776932e1 ("Rework the u-boot-fslc and u-boot-imx settings logic")
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
We need to make it more obvious what is in use, when we support both
bootloaders and for it we are now using the _pn suffix for both.
This also fixes the WIC_FILE depending on the choice otherwise image
build fails.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
We need to allow the override of the variable in 'local.conf' or other
places, so we cannot overwrite it inside imx-base.inc.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
Boot container provided by mainline U-Boot build can be used directly
int the result image file, and does not depends on the imx-boot
component provided by NXP.
Define variable to be used for conditional inheritance on the
imx-boot-container class when 'imx-boot-container' is present in
machine overrides.
Modify WKS dependency to imx-boot for mainline BSP built for aarch64 to
use imx-boot when derivative does not set the boot container
compatibility in its overrides.
Signed-off-by: Andrey Zhizhikin <andrey.z@gmail.com>
|
|
Update all recipes to pull sources from imx_5.4.70_2.3.0 branch in NXP
upstream and update SRCREV to match release tags.
Update PREFERRED_VERSION of optee for mx8 to point to 3.10.0.imx.
Following notes are additions to the version update of recipes:
--------------------------
optee-client:
- Drop CFLAGS patch as it is already applied upstream
optee-os:
- Drop gcc10 patch as it is already applied upstream
- Add dependency on python3-pycryptodomex-native
- Drop NOWERROR flag as package is reworked to disable warnings by default
- Rework mkimage load address since tee-init_load_addr.txt is no longer created
optee-test:
- Drop python3 patch as it is already applied upstream
- Remove unused patch files from layer
- Add dependency on python3-pycryptodomex-native
- Add sysroot to C and C++ flags
Fixes #686, fixes #689.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
|
- Remove redundant variable assignment
- Move creeping comment back where it belongs
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
|
Use i.MX fork to support additional machine learning demos and tiny dnn.
Signed-off-by: Chris Dimich <Chris.Dimich@boundarydevices.com>
|
|
There is no u-boot-fslc-tools recipe and thus the PREFERRED_PROVIDER is
not available for u-boot-tools.
Prevents:
| 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 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: Max Krummenacher <max.krummenacher@toradex.com>
|
|
Add a preferred provider for u-boot-mfgtool since it also has both a community and
an i.MX version.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
|
The gstreamer1.0 recipes for the i.MX forks were updated to a newer version, but
the file versions were not updated accordingly. For the NXP 5.4.47 release, the
gstreamer version is 1.16.2.imx. For NXP 5.4.70, the gstreamer version is
1.16.3.imx.
Note that the original version 1.16.imx was not appropriate either, and this
fix can also be viewed from that perspective, that the third digit of the version
should be included in the recipe version.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
|
Update PREFERRED to release 5.4.70_2.3.0.
imx-gpu-viv now has opencl-clhpp in PROVIDES. Set this as the
preferred provider.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
Set MACHINE_GSTREAMER_1_0_PLUGIN for mx8mq, mx8qm and mx8qxp machines.
Also, set PREFERRED_VERSION_gstreamer1.0 and related plugins for all
mx8 machines.
Signed-off-by: Pierluigi Passaro <pierluigi.p@variscite.com>
|
|
Use imx-gpu-viv for hardware-accelerated OpenCL implementation.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
|
The existing OpenCL recipes opencl-headers and opencl-icd-loader are dependencies
for clinfo. In order to build clinfo with imx-gpu-viv as provider, fix imx-gpu-viv
to provide the same recipe names.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
|
If using a fsl-xxx distro the prefered provider of U-Boot is
u-boot-imx. That U-Boot didn't make the switch to a unified dl/q/qp
binary and does not use an spl. For the imx6ulevk it does not use an
spl.
The below commits try to address that, however the change is not
limited to
- the fsl distro but rather uses use-nxp-bsp which can be used with any distro
- some machines which do not use u-boot-imx, e.g. colibri-imx6 now fail.
Fix this by moving the configuration into the affected distro in
meta-freescale-distro and the machines.
Fixes:
c9757ea3 ("imx-base.inc: Fix use-nxp-bsp after rework")
77e56f30 ("imx-base.inc: Limit use-fsl-bsp u-boot overrides to i.MX 6 and 7")
e5cd33c9 ("u-boot.imx: Add u-boot configuration for fsl")
Build tested with fsl-xwayland & use-nxp-bsp for imx6qdlsabreauto,
imx6qdlsabresd, and imx6ulevk.
Build tested with the fslc-xwayland & use-nxp-bsp for imx6qdlsabreauto,
imx6qdlsabresd, imx6ulevk, and colibri-imx6.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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 is an adaptation of the original recipe
https://bitbucket.org/retotech/meta-jailhouse
- add recipe for Jailhouse version 0.11
- enable for mx8mq, mx8mm, mx8mn
- add pyjailhouse/python tools like jailhouse-cell-linux
- update to python3 classes
Signed-off-by: Cristinel Panfir <cristinel.panfir@nxp.com>
|
|
We should avoid leaking NXP settings when using mainline BSP so we need
to filter it out.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
The library should not be overrided for SoCs without official BSP
releases from NXP as it is untested.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
Current assignment of the IMX_DEFAULT_BSP variables is too strong. For
example, any IMX_DEFAULT_BSP value set in local.conf currently gets
overridden by the assingment in imx-base.inc. Soften the assignment
to allow for alternative values for these variables.
Signed-off-by: Carlos Rafael Giani <crg7475@mailbox.org>
|
|
Bump revisions of optee, wayland-protocols and weston since recipes were
upgraded.
Signed-off-by: Andrey Zhizhikin <andrey.zhizhikin@leica-geosystems.com>
|
|
The i.MX 8QXP has Cortex-A35 cores plus Crypto
extensions, so enable them by default.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
|
We cannot change the default BSP based on SoC as we trim out those when
moving to the mainline BSP.
For this reason, we moved the i.MX8 forced setting to our respective
machines as they lack mainline BSP support.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
The imx-alsa-plugins use i.MX kernel specific APIs so we cannot use it
with mainline.
Now, the imx-alsa-plugins are added only when NXP BSP is in use.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
We need to postpone the expanion so we avoid cycles.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
Like other i.MX 8M SOCs, the 8M Quad has Cortex-A53 cores
and supports ARM Crypto extensions. Enable them by default.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
|
We are forcing the mainline BSP for 'mxs' and 'mx5' so it will always
use '-imx' suffix. This allows us to drop the unused values.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
The mainline BSP is the only well supported option for i.MX23, i.MX28,
i.MX51 and i.MX53 so force its use.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
The `use-mainline-bsp` must have higher priority over SoC one so it can
override settings when need.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
Machines or distros can define which BSP it should use by default. We
are intending to default for mainline BSP by default and specific
machines or DISTROs might change it if need.
Two values are considered valid: mainline, nxp
For example:
IMX_DEFAULT_BSP ??= "mainline"
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
The community forks are not being actively maintained by community and
vendors and as consequence are not being updated as need. Aiming to
reduce the maintenance burden we are dropping them as we will move to
NXP's GA kernels when using NXP BSP.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
The providers were incorrectly set to the -native recipe instead of the
nativesdk- recipe
Signed-off-by: Joshua Watt <Joshua.Watt@garmin.com>
|
Otavio Salvador
Andrey Zhizhikin
Tom Hochstein
Chris Dimich
Max Krummenacher
Pierluigi Passaro
Cristinel Panfir
Carlos Rafael Giani
Andrey Zhizhikin
Joshua Watt