The external kernel module does not build with linux 3.14, and we want
to test the upstream driver included in the kernel tree.
So for the moment disable the external kernel module, to allow start
building images in the buildserver.
https://jira.digi.com/browse/DEL-1748
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>
Now each platform is only supported in one kernel version, so there is
no need to have multiple calib files per linux kernel version.
https://jira.digi.com/browse/DEL-1747
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Now each platform is only supported in one kernel version, so there is
no need to have multiple alsa config files per linux kernel version.
https://jira.digi.com/browse/DEL-1747
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>
Also remove kernel configuration fragments for kernel 3.10. This is not
needed for 3.10 as all the configuration is done via device-trees.
https://jira.digi.com/browse/DEL-1695
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit b0031915f1c7f3eeba680161827e78bbac9eebb4)
This is a regression introduced in a74363c. The MOD_VARIANT variable was
not correctly set because in kernel 2.6.35 there is no device-tree
support.
The fix is to get the module variant from the sysfs as a fallback for
old kernels.
https://jira.digi.com/browse/DEL-1694
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit 6357d71152c38c4713fc534b78b6c2993b201aa8)
Add the following lines to add support for the HSP/HFP and A2DP profiles,
and to route the audio through the HCI SCO channel:
Enable=Source,Sink,Headset,Gateway,Control,Socket,Media
SCORouting=HCI
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The following section configures the Audio Data Path to Voice Over UART.
//Audio - Audio main config
[H:S]0041
[H:S]0004
[H:A]01 00 00 00
The syntax is explained in the AR3002 2.2 Tag definition 1.0 document from
Qualcomm/Atheros.
Other audio sections are removed as they are not being used.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Adapt u-boot bootscript after latest changes in 'mmcdev' variable
semantics. Now the boot media device is stored in 'mmcbootdev' variable.
Also set the device tree filename depending on the hardware variant.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Support new memory chips for 'ccardimx28js'.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit b7d108c35f6a26a78a4fbab399fd2c0878976a67)
Some CC6 variants have wireless but not bluetooth. Those variants need a
different calibration file.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit a74363cf4a9b239edf9d628f84fe7e88002c0f5c)
Add post-installation script that runs on first boot to reconfigure the
u-boot environment depending on the media (EMMC,SD) the target is
booting from.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit 8486d120355d80ea8ad5864596c8486a1d3c0db2)
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 previous class 1 settings for the atheros bluetooth resulted in
output power higher than what is allowable in all regulatory
domains where class 1 devices are allowed on the CC6. The updated class 1
regulatory settings here reduce the maximum output power to levels
which pass when tested at an external lab.
This change resolves CCIMX6-389.
Signed-off-by: Paul Osborne <Paul.Osborne@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>
Those packages are not machine specific, so there is no need to set
PACKAGE_ARCH to ${MACHINE_ARCH}.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
athtestcmd and wmiconfig are proprietary tools from Atheros. When
installed from GitHub we use prebuilt binaries because we cannot provide
the source code to the customers.
The prebuilt binaries need to be platform dependent, because the
'ccardimx28' uses soft-float binaries while the 'ccimx6' uses hard-float
binaries. Otherwise there is a failure:
root@ccimx6sbc:~# /usr/sbin/athtestcmd
-sh: /usr/sbin/athtestcmd: not found
While on it, removed the checksums for the binaries, as Yocto does
not verify checksums for local files by default, only for downloaded
files.
https://jira.digi.com/browse/DEL-1586
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit 8a3a124c75a885a619b41bf1e17118f1b3dec13c)
The SD card images support added a dependence to mkimage native tool.
Otherwise the build may fail with:
mkimage: not found
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 simplifies the code and as an extra allows to override the default
root password from the project's local.conf (setting MD5_ROOT_PASSWD
variable)
https://jira.digi.com/browse/DEL-1558
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Poky added a new class that provides the same functionality we
implemented in our 'dey-image' class. So just use that class instead
of reimplementing it in our layer.
https://jira.digi.com/browse/DEL-1558
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Remove 'dey-test' image feature and create a SARES bbclass with the
same functionality. This makes easier the creation of images suitable
for SARES testing just adding:
INHERIT += "sares-image"
to your project's local.conf
https://jira.digi.com/browse/DEL-1558
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
With yocto 1.8 we need to pass CC and LD from yocto environment to
imx-bootlets makefile. Otherwise it fails:
arm-dey-linux-gnueabi-ld: cannot find -lgcc
make[1]: *** [output-target/linux_prep] Error 1
https://jira.digi.com/browse/DEL-1558
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Yocto 1.8 is more strict in the syntax when you append more flags to the
CFLAGS variable, because with previous yocto versions these packages
used to build fine and now fail with:
run.sstate_create_package: Syntax error: "(" unexpected
Use a different EXTRA_CFLAGS variable for our custom flags instead of
the standard CFLAGS.
https://jira.digi.com/browse/DEL-1558
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
We need to append our config to EXTRA_OEMAKE variable instead of
overriding it, because otherwise we lose some config from the
environment (e.g. KERNEL_SRC) and the build fails with:
make: *** M=...kernel-module-.../git: No such file or directory
Also remove redundant PACKAGE_ARCH setting, as it's inherited from
module-base class.
https://jira.digi.com/browse/DEL-1558
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Alex Gonzalez
Javier Viguera
Paul Osborne