* Merge u-boot-dey-rev_2015.04.inc into the recipe. There is no need to
split the recipe, as there is no other recipe using this u-boot code.
* Update uboot configurations to the new format '_defconfig'. Also add
the new 2GB variant.
* Remove PREFERRED_VERSION_u-boot-dey for CC6, as there is only one
version available for this platform.
https://jira.digi.com/browse/DEL-1829
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Linux 3.10 is still available via project's local.conf.
PREFERRED_VERSION_linux-dey = "3.10"
KERNEL_DEVICETREE = "..."
https://jira.digi.com/browse/DEL-1748
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Platform defconfig corresponds to sha1 'e1506ff' in the kernel.
At this point linux-3.10 continues to be the default, some device-tree
files were renamed and the external atheros module does not compile with
linux-3.14, so to use this kernel with dey-1.8, following lines are
needed in the project's local.conf:
PREFERRED_VERSION_linux-dey = "3.14"
KERNEL_DEVICETREE = " \
imx6dl-ccimx6sbc-wb.dtb \
imx6dl-ccimx6sbc-w.dtb \
imx6q-ccimx6sbc.dtb \
imx6q-ccimx6sbc-wb.dtb \
imx6q-ccimx6sbc-wb-ldo-bypass.dtb \
imx6q-ccimx6sbc-w.dtb \
"
MACHINE_FEATURES_remove = "wifi"
https://jira.digi.com/browse/DEL-1748
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The 'resize2fs' command we use to resize the filesystem on first boot
has been moved from standard 'e2fsprogs' package to its own
'e2fsprogs-resize2fs', so this is the one we need to include now.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Use Yocto's UBOOT_CONFIG new functionality to select the u-boot
configuration to build.
https://jira.digi.com/browse/DEL-1584
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Remove the current DEY variants support and framework for CC6 because in
following commits we will add support for all *hardware* variants in
just one set of DEY images for CC6.
https://jira.digi.com/browse/DEL-1569
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>
Also remove support for device tree variants as it's not needed. We will
only have different device tree for the different CPUs, but not for the
different variants of the same CPU.
https://jira.digi.com/browse/DEL-1569
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This synchronizes the machine configuration files with the latest
changes in meta-fsl-arm for yocto 1.8
https://jira.digi.com/browse/DEL-1558
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Variant 0x8 does not have wireless/bluetooth, but it uses the same
device tree than the other variants.
https://jira.digi.com/browse/DEL-1524
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit 3ba5bff51ebbe6be8325128ae3beb950993607d2)
Variant 0x5 (Furuno) does not have bluetooth, but the device tree in the
kernel is the same than the variant with bluetooth.
https://jira.digi.com/browse/DEL-1524
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit 7de11f08e95fecb8d4895556292a488a91af6817)
This completes the support for ccimx6sbc variants:
* support device tree variants
* split variants '0x01,0x02,0x04' group in two different groups (with or
without kinetis)
https://jira.digi.com/browse/DEL-1359
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit 3f20015411f4e270b2e2c8faf292678c75ff2aff)
https://jira.digi.com/browse/DEL-1359
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit 015d029255eb407cca4c986562a304aef7de3940)
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>
Notes:
* This version of u-boot does not support comments in scripts
* Enabled EXT4 in kernel config (for the SDCARD rootfs)
https://jira.digi.com/browse/DEL-197
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
In Yocto 1.7 meta-fsl-arm replaced udev-extraconf bbappend with a new
package (udev-rules-imx). So we need to adapt our own bbappend to these
changes so all the needed udev rules are in place.
https://jira.digi.com/browse/DEL-1336
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
We inherited from DEL the requirement to build more than one flash image
for the same rootfs contents depending on the EBS of the flash chip.
Yocto does not have support to generate more than one flash image so we
had to create functions in the image_types_digi bbclass to provide this
feature.
This commit removes that functionality and uses the standard yocto
support to generate ubifs and jffs2 flash images. The way to customize
the flash parameters is via EXTRA_IMAGECMD_jffs2 and MKUBIFS_ARGS
variables. In our case those variables are already set depending on the
different hardware variants.
https://jira.digi.com/browse/DEL-232
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>
The interfaces file is now dynamically created for eth0, eth1 and wlan0. By
default they are configured if enabled in the machine features, and have
the same static configuration as before.
The static IPs can be configured as follows:
ETHn_STATIC_IP = "<ip address>"
ETHn_STATIC_NETMASK = "<netmask>"
ETHn_STATIC_GATEWAY = "<gateway>"
WLAN0_STATIC_IP = "<ip address>"
WLAN0_STATIC_NETMASK = "<netmask>"
To configure dynamic IPs you can use the following configuration in your
local.conf:
ETHn_DHCP = "dhcp"
WLAN0_DHCP = "dhcp"
https://jira.digi.com/browse/DEL-1178
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This will be the preferred version for ccardimx28. Then use platform
override to set the one for ccimx5 and ccimx6.
Not having a platform override in the machine config file allows to do
a simple version override in the project's local.conf file with:
PREFERRED_VERSION_u-boot-dey = "2009.08"
Otherwise, if we use a platform override in the machine config that
takes precedence over a normal override in the project's local.conf
and we would have needed something like:
PREFERRED_VERSION_u-boot-dey_ccardimx28 ?= "2013.01"
in the project's config.
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>
Add platform family to SOC_FAMILY, so it's part of the MACHINEOVERRIDES
variable and it can be used to generalize bitbake recipes.
https://jira.digi.com/browse/DEL-1105
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>
While on it, rework and simplify atheros firmware recipe:
* remove 'unknown' version (renamed recipe)
* do not create empty debug and development packages
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>
Currently Vivante does not provide a valid GL API so Xorg fails to link
against it, we cannot workaround it easily in newer Xorg version so
instead of maintaining a pile of patches for it we use 1.14.4 version
as an interim solution.
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>
Provides fw_printenv/fw_setenv utilities to read/write the u-boot
environment from Linux.
https://jira.digi.com/browse/DEL-800
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
At the moment this image is a VFAT file system containing the kernel
and the device tree blobs.
https://jira.digi.com/browse/DEL-932
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This package is now used in both ccimx6adpt and ccardimx28js.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
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>
nvram, ubootenv and update_flash are machine related utilities. They
need to be configured per-platform via MACHINE_EXTRA_RDEPENDS and thus
leaving packagegroup-dey-core as much platform-agnostic as possible.
This also allows to skip these utilities for platforms not using them.
https://jira.digi.com/browse/DEL-915
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Also remove 'gplay' utility from dey-image-graphical. It's a command
line application suitable to be used on minimal (non-X) images.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Use a variable to select GPU flavour (X11, framebuffer).
No functionality change, just coding style.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
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>
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>
This is still a runtime-recommend of udev package so it gets installed
in udev based images (graphical) and not installed in mdev based images
(minimal).
https://jira.digi.com/browse/DEL-825
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 UBOOT_LOADADDRESS and UBOOT_ENTRYPOINT variables are only used in
the kernel recipe, so remove from the machine configuration files.
Also, use the defconfig from the kernel tree which compiles all the
support by default and expects the device tree to be configured with
the desired support. Hence, remove all the empty configuration fragments
files.
https://jira.digi.com/browse/DEL-577
Signed-off-by: Alex Gonzalez <alex.gonzalez@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>
Mostly cosmetic changes to clear it a bit so customers can use it as
documentation for what variant they need to configure in their projects.
Also a couple of minor fixes: 'ext-eth' typo and duplicated 'e' variant
for ccimx53js.
https://jira.digi.com/browse/DEL-460
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Running:
bitbake -c cleanall packagegroup-machine-base
was failing due to those trailing backslashes.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The previous "+=" format was doing a complete variable override instead
of an append. Features like usbhost or usbdevice were disappearing.
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>
Do not generate them until they are properly tested and working.
Fixes https://jira.digi.com/browse/DEL-192
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>
U-Boot has a set of pre-defined make targets per platform that allow
to configure u-boot for different variants (128sdram,4Kpage,dbg etc.)
This change allows to use a UBOOT_CONFIG_VARIANT variable in your
local.conf file to choose which variant to build.
Signed-off-by: Alex Gonzalez <alex.gonzalez@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>
In this way the layer should still be able to compile the default
machines supported by meta-fsl-arm.
Signed-off-by: Alex Gonzalez <alex.gonzalez@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