Also remove QT4 phonon patches and qtmediaplayer demo as they depend on
gstreamer-0.10.
https://jira.digi.com/browse/DEL-1890
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 2.0
https://jira.digi.com/browse/DEL-1890
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
ccimx51js and ccimx53js are not supported in this version of DEY.
Support for those platforms is in previous versions of DEY.
https://jira.digi.com/browse/DEL-1890
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Split the ATH6KL firmware files to a different recipe and package so
they can be used regardless of what driver we are using (the external
module or the upstream driver).
Reuse the 'firmware-atheros' recipe which was creating a package with
bluetooth firmware, to create the package with wireless firmware as
well.
Also remove 'ccimx6' as compatible machine for the external atheros
module, as the module does not even compile with the kernel version we
are using (3.14).
https://jira.digi.com/browse/DEL-1858
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Which wireless module to use belongs more to the machine config files in
the BSP layer, than to the generic wireless packagegroup.
https://jira.digi.com/browse/DEL-1858
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
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
There is only one u-boot supported for each platform, so there is no
need to explicitly set the u-boot preferred version.
As a result it was needed to rework the nvram recipe which was using the
removed PREFERRED_VERSION_u-boot-dey variable.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
There is only one kernel supported for each platform, so there is no
need to explicitly set the kernel preferred version.
Also:
* Remove IS_KERNEL_2X variable which is no longer needed.
* Simplify jenkins build script, now that we do not need to build two
kernel versions for ccardimx28.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Instead of creating a new recipe for u-boot fw-utils (fw_printenv) just
bbappend the recipe in Poky.
https://jira.digi.com/browse/DEL-1829
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
* 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>
https://jira.digi.com/browse/DEL-1734
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit 35a78b13f72963205dc1ae1e05ee851ca6cc4f28)
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>
This is needed in the context of CC6 variants 0x7 and 0x9 (EMMC-less).
Changes:
* Do not use 'meta-fsl-arm' image generation class: removed include and
override SDCARD generation function
* Use same VFAT boot image for EMMC and SD card. The u-boot bootscript
has been adapted to be able to boot Linux from both SD and EMMC.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit 8b8456b8fd90facd92dfc87632effa582ca60475)
This will allow in following commit to use the same VFAT boot image for
EMMC and SD. Until now we were creating different boot images for EMMC
and SD card images.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit 13e9ec7608d42430c2a01a728d030752a71f7948)
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)
It has never been a mirror of upstream packages.
It's the URL of packages needed for the BSP. These packages are mostly
Digi specific and not provided in any other location.
https://jira.digi.com/browse/DEL-1493
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit d4cf9a88c9db39c6ecfd0099437d82af81c96e85)
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>
Revert to the old way of setting the console for ccardimx28js. Configure
the console on the generic ttyS0 port name and let the device managers
create a symbolic link to the correct device at runtime.
Trying to set it statically at compile time lead to some side effects
with some packages not being recompiled after a change of the preferred
kernel version in the project's local.conf (e.g. udev-extraconf and
sysvinit-inittab).
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
SERIAL_CONSOLES_CHECK is new functionality provided by Yocto, but it
needs '/proc/consoles' supported by the kernel. Our kernel 2.6.35 does
not support '/proc/consoles' so rework the serial console configuration
to work with both kernels (2.6.35 and 3.10).
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>
The i.MX6 has an internal PMU with LDOs to supply voltages to the different
ARM sybdomains. There are two possible configurations, to use this internal
LDOs or to use the external PMIC to supply the voltages (LDO bypass).
The default is to boot with LDO bypass, and the device tree with the -dts
suffix will boot with the i.MX6 internal LDO.
Signed-off-by: Alex Gonzalez <alex.gonzalez@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>
Javier Viguera
Alex Gonzalez