This synchronizes the machine configuration files with the latest
changes in meta-fsl-arm for yocto 1.8
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The IMAGE_FSTYPES variable for ccimx51js and ccimx53js was not correct,
it was taking the default one from Poky (IMAGE_FSTYPES="tar.gz")
instead of the one in 'imx-digi-base.inc' file. This happened because we
were using the weak '??=' assignement while the default in Poky was
using '?='.
Also rework a bit how this variable is set, so it is easily overriden on
project config files or initramfs recipes.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Kernel 3.10 does not fail to build perf features (as kernel 2.6.35
does), so there is no need to disable them for platforms using that
kernel version.
https://jira.digi.com/browse/DEL-1418
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This synchronizes the machine configuration files with the latest
changes in meta-fsl-arm for Dizzy maintenance branch.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
FSL has this enabled but in our case it fails to build for ccardimx28js
using linux 3.10 with error:
fatal error: linux/mxcfb.h: No such file or directory
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This synchronizes the machine configuration files with the latest
changes in meta-fsl-arm for Daisy maintenance branch.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
It was broken after the upgrade to Yocto 1.6 because the framework to
generate images in Yocto 1.6 changed.
https://jira.digi.com/browse/DEL-1032
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
It was added to fix [DEL-898] but it is no longer needed after the
underlying changes in the rootfs hierarchy (added '/run' mountpoint)
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Previously jffs2 images flashed from u-boot were not booting Linux. The
kernel was unable to mount the rootfs.
There have been some patches lately in the kernel that fix this problem,
so build jffs2 images.
Nevertheless the default image type is still ubifs when using linux 3.x.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
At the moment our kernel 3.10 on ccardimx28js does not support jffs2
images, so do not build them.
Signed-off-by: Javier Viguera <javier.viguera@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>
This fixes a bug in 'ccardxmx28js' where the wpa_supplicant was using
the wrong driver 'wext' instead of the 'nl80211' (for atheros)
https://jira.digi.com/browse/DEL-220 #resolve
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>
Javier Viguera
Alex Gonzalez