https://jira.digi.com/browse/DEL-1734
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit 35a78b13f72963205dc1ae1e05ee851ca6cc4f28)
This is a Consumer quad-core 1.2GHz, 4GB eMMC, 2GB DDR3, -20/+85C variant
with bluetooth and wireless, no kinetis.
Signed-off-by: Alex Gonzalez <alex.gonzalez@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 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)
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>
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>
The way the kernel is built in yocto 1.8 has changed. Now the
build is done under ${WORKDIR}/build while the source code is at
STAGING_KERNEL_DIR, so we need to modify the '.config' in the build
directory instead of in the source directory.
This fixes:
kernel-source is not clean, please run 'make mrproper'
make[2]: *** [prepare3] Error 1
make[1]: *** [sub-make] Error 2
https://jira.digi.com/browse/DEL-1558
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>
A post-down script was unloading the Atheros wireless driver
when the network interfaces were brought down.
On rare occasions the 'rmmod' command was not able to complete
and may leave the system in an unexpected state.
This patch removes the post-down script for the ccardimx28 platform
and leaves it only for the ccimx6 platform, where the unloading
is wanted to reset the driver after suspend.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-1314
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>
The removal was added as a workaround to avoid installing a generic
asound.conf that was conflicting with our cards.
This is no longer needed as poky installs an empty asound.conf and
meta-fsl-arm overrides it with per-platform asound.conf files.
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>
This bbappend was added to be able to native build the util-linux
package in our old buildserver (with Debian 6). This is no longer needed
as we migrated our buildserver to newer Debian.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Add possibility for other layers to add additional features for UBIFS creation,
e.g. "-R <rp_size>" for super-user reserved pool.
Signed-off-by: Robert Hodaszi <robert.hodaszi@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>
By removing the driver on ifdown and loading it on ifup we workaround some
problems found in long run suspend stability testing.
https://jira.digi.com/browse/DEL-1084
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 updates the driver to upstream AR6003-ISC-v3.4p6-b3.4.0.225.
https://jira.digi.com/browse/DEL-1127
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This adds the calibration file for US regulatory (still missing the
world-regulatory calibration file)
https://jira.digi.com/browse/DEL-1102
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>
Those hacks were added to fix a problem when building development images
(with 'dev-pkgs' image feature enabled). In that case the developemnt
packages (libdigi-dev and microwindows-dev) have a dependence on the
normal packages (libdigi and microwindows). But those packages are not
created by default because they are empty, thus the needed ALLOW_EMPTY hack.
Fix the problem by just resetting the runtime dependences of the -dev
packages. This allows to not create empty libdigi and microwindows
packages.
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>
User-space has been updated in meta-fsl-arm for the general availability
(GA) FSL release, so use the kernel branch with the GA support.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The 'v3.10/master' master branch has been updated with the latest
general availability (GA) release from FSL, but the user-space is not
ready yet, so using the new kernel the build is broken:
imx-lib: error: 'PXP_IOC_GET_CHAN' undeclared
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Needing to set the branch where a specific SHA1 revision is contained is
a unnecessary constraint that can be bypassed setting 'nobranch=1' in
the SRC_URI.
We do that for all the external repos (GitHub) plus the internal ones
for the im-xbootlets and the atheros kernel module (as those two repos
are stable enough and we are not developing actively on them).
For U-Boot and Linux we keep the SRCBRANCH framework for internal repos
as this is needed for the AUTOREV yocto feature.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Starting with Yocto 1.6 there is a need to configure in which branch a
specific SHA1 revision is included. We need a framework to set such
branches both for internal git repos and for external ones (Github).
If the branch is not specified in the SRC_URI, the do_fetch task may
fail even though the SHA1 revision exists in the repository.
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>
By default EMMC boot partition is locked. This prevents fw_setenv
utility to configure the u-boot environment from Linux.
This commit adds a patch that unlocks the EMMC boot partition just
before writing into it and then locks it again once the environment is
written.
https://jira.digi.com/browse/DEL-1021
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The setlocalversion script in u-boot 2009.08 did not have the
'--save-scmversion' parameter so the build was failing.
But for that version the whole do_compile_prepend can be removed because
it's not needed at all.
While on it, update the revisions for versions 2009.08 and 2013.01 to
include a fix done in 'setlocalversion' script.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Otherwise building Yocto 1.6 for ccardimx28js fails with:
ERROR: Logfile of failure stored in:
/home/jviguera/projects/yocto/master/gui/ccardimx28js/tmp/work/ccardimx28js-dey-linux-gnueabi/kernel-module-atheros/1.0-r1/temp/log.do_fetch.38442
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This fix an error building 'nvram' for ccardimx28js:
ERROR: Fetcher failure: Unable to find revision ... in branch master even from
upstream
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This cleans following warning:
Use of PRINC is deprecated.
The PR server should be used to automatically increment the PR.
See: https://wiki.yoctoproject.org/wiki/PR_Service
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The boot partions name has been changed in u-boot, so change it also
here to match current u-boot.
https://jira.digi.com/browse/DEL-949
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Building u-boot with Yocto does not show the version string in the
u-boot header. This is due to how Yocto compiles u-boot. It creates a
.scmversion file which may contain LOCALVERSION strings but in our case
it's empty. Later at build time u-boot's setlocalversion script detects
that file exists and exits with no further action (because it assumes
the file contains the version string).
https://jira.digi.com/browse/DEL-1007
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Fetch the source from the dey-1.6/maint branch which contains a fix
for a kernel oops introduced by the Yocto GCC 4.8.1 compiler.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The build was failing in our Jenkins server (Debian 6) with:
error: 'MS_PRIVATE' undeclared
error: 'MS_REC' undeclared
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The way to create rootfs images has changed in poky master. The whole
process has been reworked in python and the hook to create a new image
is the IMAGE_CMD variable. The old 'runimagecmd' shell function has
been deleted so we cannot override it in our custom class.
https://jira.digi.com/browse/DEL-996
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This workaround is not needed anymore as the git fetcher bug is fixed in
poky's master branch.
This reverts commit 982af63902.
https://jira.digi.com/browse/DEL-996
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>
PR was based on meta-fsl-arm's 'linux-imx.inc' INC_PR, but this was
removed after Dora, so we need to remove PR from our kernel recipes to
avoid a bitbake parser error:
${INC_PR}.0/git')} exception SyntaxError: EOL while scanning string literal
https://jira.digi.com/browse/DEL-996
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
linux-dey.inc is a copy of meta-fsl-arm's linux-imx recipe file, so
instead of copying the whole recipe just use that (including the file)
and code the differences.
While on it, add RDEPENDS_kernel-base="" to remove the dependence of the
rootfs image recipes on the linux image. We don't need/use the kernel
image in the rootfs as we load it from a different partition. This makes
rootfs images a bit smaller.
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>
These files were needed in previous versions of Yocto to overcome
different problems. Remove them as the default ones in current Yocto
version are good enough for our platforms.
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>
change the directory (cd) and make the symbolic link in a subshell to
preserve the current working directory for any subsequent command.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
We have all the kernels configured with DEVTMPFS support, so there is
no need to have static nodes in the image files. They are not used at
runtime because a TMPFS is mounted at '/dev'.
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>
bitbake git's fetcher uses 'ls-remote' to get the branch revision to
checkout. If the repository has two branches ending equally the 'git
ls-remote' just picks the first one regardless of that being the correct
one.
In our case we were bitten by this bug because our git repo has:
...sha1-revision... refs/heads/android/v3.10/master
...sha1-revision... refs/heads/v3.10/master
and the fetcher was using the android branch instead of linux's
v3.10/master.
A patch has been sent upstream but while that gets applied to Dora
maintenance branch the workaround here is to set the absolute path in
the kernel's bitbake recipe.
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>
These utilities are very tight to the hardware so they need to be in
the BSP layer. This way they can also be installed in a poky distro
core-image-minimal without meta-digi-dey layer.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
SERIAL_CONSOLE variable has been deprecated in poky. The new
SERIAL_CONSOLES allows to configure multiple devices.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The do_update_dts function was hardcoded for ccardimx28js. We need to
make it mxs specific so the recipe can be used for other platforms that
do not share the same device tree configuration (for example the
upcoming ccimx6js)
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Instead of using a SHOWCURSOR variable hardcoded from the
HAVE_TOUCHSCREEN environment var, allow to set it freely in formfactors
config file and use it to show (or not) the cursor in the graphic
session.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Formfactor config files are needed in now so the touchscreen calibration
is loaded on target's boot. Otherwise the touch is not calibrated.
https://jira.digi.com/browse/DEL-910
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The bbappend only has a patch that does not apply anymore to the new
version of the package upstream (11.09.02).
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
To be sure the 'cfg80211' module is settled down before the
'ath6kl_sdio' module tries to use it.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Version v3.4p6 seems to have some problems with WEP encription. Version
v3.4p4 seems to work better with WEP, so revert to that version.
https://jira.digi.com/browse/DEL-843
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
There seems to be a race condition in the load of the 'cfg80211' and
'ath6kl_sdio' modules. If we try to load the atheros module before the
cfg80211 is settled down, the driver crash.
The workaround is just separate the load of both modules in two separate
'modprobe' commands and add a small delay between them.
https://jira.digi.com/browse/DEL-814
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Not well supported yet and cleans a debug line:
ath6kl: ath6kl_cfg80211_connect: sme->mfp = 0
https://jira.digi.com/browse/DEL-815
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>
The Linux kernel revision was splitted from main bitbake recipe to its
own linux-dey-rev file so that file could be used for linux-headers
recipe to build the toolchain using custom kernel headers (from our
repository).
That is not the recommended way to build a toolchain:
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=babbf7a46acaefd9b36031483cafce053f607e66
and we are not using our kernel headers to build the toolchain anymore,
so just melt the linux-dey-rev files into the linux-dey bitbake recipes
for cleanness and easier maintenance.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The wireless module occasionally fails to load in kernel v3.10.
If that is the case, unload the driver and load it again (up to
five retries).
Notes:
- Only the ath6kl_sdio module needs to be unloaded and reloaded.
- The chip is not issued a power cycle via CHIP_PWD_L because
this demonstrated to cause failure, instead of improving
behaviour.
- The 2-seconds sleep after unloading the driver is a security
measure to avoid other problems seen during test cycle.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
Reviewed-by: Javier Viguera <javier.viguera@digi.com>
https://jira.digi.com/browse/DEL-820
Committed a patch in linux-dey repo to fix perf build. At the same
time update linux-dey revision to get the perf fix.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This was supported in kernel 2.6.35 (FSL release) but not in community
kernel 3.10
https://jira.digi.com/browse/DEL-839
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Move the BOARD selection out of the bootlets recipe so it can be used
from machines defined in other layers.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
So the IMX udev rules can be used without meta-digi-dey layer. For
example when building core-image-minimal with poky distro.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Move the flash parameters to the machine configuration files so it's
easier to create derivative machines and use the image bbclass to create
flash images.
(based on a patch from Seth Bollinger <sethb@digi.com>)
https://jira.digi.com/browse/DEL-682
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
They conflict.
Warn the user about the problem and let they change the device tree
manually.
https://jira.digi.com/browse/DEL-840
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
list.h: In function 'INIT_HLIST_NODE':
list.h:582:12: error: 'NULL' undeclared (first use in this function)
list.h: In function 'hlist_move_list':
list.h:661:15: error: 'NULL' undeclared (first use in this function)
list.h: In function 'hlist_move_list':
list.h:661:15: error: 'NULL' undeclared (first use in this function)
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
To avoid conflicts between the two flavous (X11, framebuffer). Also fix
bitbake parsing error in the buildserver:
ERROR: Nothing PROVIDES 'virtual/libx11' (but
amd-gpu-x11-bin-mx51_11.09.01.bb DEPENDS on or otherwise requires it)
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>
This version does not properly work with v3.10 kernel, while
the newer version 3.0.35-4.1.0 does work for old and new
kernels.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
Reviewed-by: Javier Viguera <javier.viguera@digi.com>
https://jira.digi.com/browse/DEL-797
This set of patches are forward port of patches for old version
10.12.01 and to make it work with v3.10 kernel.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
Reviewed-by: Javier Viguera <javier.viguera@digi.com>
https://jira.digi.com/browse/DEL-797
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>
Also change the default ccardimx28js variant to 'web1' (wireless, second
ethernet, bluetooth and 1-wire)
https://jira.digi.com/browse/DEL-819
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>
Most SRC_URI defaults to DIGI_LOG_GIT. This patch sets a more generic
name (DIGI_GIT) that defaults to DIGI_LOG_GIT, but is configurable by
someone who might want to tune it (DIGI_MTK_GIT, etc.).
Signed-off-by: Seth Bollinger <sethb@digi.com>
New kernels don't get CPU information from U-Boot ATAGS and
so the /proc/cpuinfo file does not have the Hardware/Revision
lines filled in.
This patch gets the CPU model from the device tree information
at /proc/device-tree/compatible.
For backwards compatibility, if the CPU model cannot be retrieved
from this file, we try to get it from /proc/cpuinfo.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
Reviewed-by: Javier Viguera <javier.viguera@digi.com>
https://jira.digi.com/browse/DEL-797
In ccardimx28 depending on the kernel version the console is on 'ttyAM0'
or 'ttyAMA0'. Use the standard serial port name ttyS0 for login (through
inittab) and let the device handlers create the symlink to the correct
device.
This allows to boot the same rootfs regardless of the kernel version.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
wmiconfig is Atheros proprietary code so the recipe builds from source
if DIGI_INTERNAL_GIT is defined or uses a prebuilt binary otherwise.
https://jira.digi.com/browse/DEL-640
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
We are now using yocto kernel headers (3.x) in the toolchain so the
patches need to be applied regardless of the version of the running
kernel.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Javier Viguera
Alex Gonzalez
Paul Osborne
Hector Palacios
Robert Hodaszi
Seth Bollinger