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>
Alsa-utils tools once compiled are distributed between a bunch of
different subpackages. Then 'alsa-utils' as a final package is just
a meta-package that depends on all of the different subpackages.
So instead of RDEPEND'ing on the alsa-utils metapackage, depend on just
a few of the alsa-utils subpackages.
This removes for example the 'alsa-utils-alsaconf' package that was
bringing bash into our rootfs.
Removing bash solves the problem of the lines-not-wrapped on the serial
console because now we use busybox' shell in the serial console.
https://jira.digi.com/browse/DEL-610
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
In function 'gst_v4l2_fill_lists':
error: 'V4L2_CID_HCENTER_DEPRECATED' undeclared (first use in this function)
error: 'V4L2_CID_VCENTER_DEPRECATED' undeclared (first use in this function)
https://jira.digi.com/browse/DEL-585
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
In Linux 2.6.35, the kernel module accepting the parameters on load
was 'ath6kl_sdio' while in 3.10 is 'ath6kl_core'.
So we need to apply the load parameters to either module depending on
the kernel version.
This is solved by configuring the modprobe configuration file
'/etc/modprobe.d/atheros.conf' with the parameters to the correct
module instead of passing them in the command line.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The bbappend was only cleaning-up some bitbake warnings. A patch has
been accepted upstream (meta-fsl-arm) to do the same.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
With the old version of the kernel (2.6.35) we build an external atheros
kernel module, while with the new kernel (3.10) the atheros driver is
included with the kernel sources.
However, the new driver needs the firmware files and the driver load
scripts that are stored with the old driver.
So put a dependence on kernel-module-atheros regardless of the kernel
version and then rework the kernel-module-atheros recipe to build the
whole driver for the old kernel or only the firmware for the new kernel.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The MACHINE_ESSENTIAL_EXTRA_* vars need to be only in the
'packagegroup-dey-core' recipe not in the rest of the packagegroups.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This is needed so the kernel modules configured in the kernel defconfig
get added to the rootfs image.
At the same time there is no need to add the usb gadget modules
separately because they are added in the machine extra recommends as
well.
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>
move ccardimx28js specific patch under PN-PV subdirectory. Otherwise it
fails to find the patch (this version of yocto restricts the FILESPATH
where to look for files)
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
ERROR: Fetcher failure: Unable to find file file://atheros anywhere
The FILESPATH variable (used as the search path for files referred to
in SRC_URI) is now (dylan) more restrictive, so move the files where
they can be found.
Signed-off-by: Javier Viguera <javier.viguera@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>
Javier Viguera
Seth Bollinger
Alex Gonzalez