This is hidden using Poky distribution because Poky has X11 distro
feature and then other x11-related dependences pulls in intltool-native.
In our case DEY distro does not have X11 feature and thus
intltool-native is not part of libsoup dependences. Then sometimes fails
and sometimes not depending on the bitbake threads (BB_NUMBER_THREADS)
and other race conditions.
Adding the dependence explicitly fixes:
run.do_configure: intltoolize: command not found
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The availability of some examples depends on the kernel version, so we
need to add the dependence to the packagegroup as well.
This allows to build two ccardimx28 projects one for kernel 2.x and the
other for 3.x sharing the state-cache. Otherwise the first project
builds correctly but the second one fails.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
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>
'simple-agent' python script included with this package depends on
python-pygobject and python-dbus
https://jira.digi.com/browse/DEL-643
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The initscripts package includes a '/etc/init.d/umountfs' script used
for reboot/poweroff purposes. That script calls the 'umount' command
but seems that the combination of busybox' umount + linux-3.x fails in
this script (it hangs without completing the reboot/poweroff).
So as a workaround use the umount command from util-linux package
https://jira.digi.com/browse/DEL-633
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
To get the latest changes: logo, mac-address, wireless...
Also synchronize the defconfig with the one in the kernel tree.
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>
Actually this is a workaround that probably needs to be generalized. But
at the moment the ccardimx28 is the only platform we have in linux 3.x
so it's enough.
https://jira.digi.com/browse/DEL-560
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
If people are creating derivative machines in their layer, make
COMPATIBLE_MACHINE more flexible. Use SOC_FAMILY instead of specific
machine types. This allows users to more easily share these recipes.
https://jira.digi.com/browse/DEL-676
Signed-off-by: Seth Bollinger <sethb@digi.com>
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The package is no longer available in the official cherokee site,
so download it from a mirror.
https://jira.digi.com/browse/DEL-584
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The dey-examples-adc and dey-examples-gpio packages are not meant to work
with a 3.10 kernel.
https://jira.digi.com/browse/DEL-574
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Modify the atheros and bluetooth init scripts to fetch the hwid details
from the device tree.
https://jira.digi.com/browse/DEL-572
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The acpid applet will run at startup and will listen for power input
events.
On arrival, it will timestamp the press event, wait for the release event
and decide whether to suspend or poweroff based on the time elapsed.
https://jira.digi.com/browse/DEL-34
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Similar commit was done in DEL.
Japanese law limits the maximum transmit power for Bluetooth to 3 mW.
The cert field in OTP will be set to 2 when units are manufactured
for Japan.
Updated the bluez init script to configure Bluetooth for class 2
operation if the cert field is set to 2, and to delete the class 1
configuration file since it would be illegal to use it in Japan.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>