Those boolean helper variables can be used in different recipes so move
them to a common place.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The machine variant is most specific than machine name.
Before: MACHINEOVERRIDES="armv5:mxs:wb:ccardimx28js"
After: MACHINEOVERRIDES="armv5:mxs:ccardimx28js:wb"
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The build was failing for any IMX platform because it was trying to
build a bootstream u-boot.
The u-boot variables (UBOOT_*) used by yocto were incorrectly set,
so I reworked and simplified them to fix the bug and ease maintenance.
https://jira.digi.com/browse/DEL-562
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
We need separate linux-libc-recipes if we want to support different
kernels.
On the 1.4 meta-fsl-arm layer this recipe will disappear, so review then.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The final product will be called "Digi Embedded for Yocto" or DEY for
short.
This commit renames all relevant files.
https://jira.digi.com/browse/DEL-474
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
I have split the machine configuration in two:
-The module machine configuration include, for example ccimx53.inc
-The machine configuration (for example cimx53js.conf) which includes
the variant configuration.
This will allow for customers to create their own machine keeping the
module include file.
The variant can be configured in the local.conf file with a
MACHINE_VARIANT variable.
The variant names are made up of the interface initials as follows:
w: wifi
e: externel ethernel
b: bluetooth
1: 1-wire
a: accelerometer
g: GPU
v: VPU
128: 128MB RAM
4k: 1024MB NAND (only for MX51 JTAG flash)
For details regarding the supported variants, each machine configuration
file contains a comment with a variants table.
https://jira.digi.com/browse/DEL-330
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
So they don't depend on the machine files from meta-fs-arm layer.
This allows to override some settings in project's local.conf file.
https://jira.digi.com/browse/DEL-219 #resolve
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The mx5 GPU libraries provide OpenGL ES1, OpenEGL and OpenGL ES2 only
so we need to ajust the PREFERRED_PROVIDER.
There is an equivalent commit in FSL layer.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
- imx-digi-base includes imx-base and contains the overrides.
- mxs-digi-base includes mxs-base and contains the overrides.
- digi-defaults contains the overrides to fsl-default-settings,
fsl-default-providers and fsl-default-versions.
- The machine configuration files include the digi includes and also
contains the UBOOT load addresses overrides.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>