This package provides 'ubiformat' command which is needed by
'update_flash' for UBI images.
https://jira.digi.com/browse/DEL-816
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
We are now using the standard yocto kernel headers so the patch to build
the plugin with new kernel headers is not needed.
The rest of the changes in the bbappend (removing gconf dependence) were
needed in yocto-danny, but not in yocto-dylan because the gconf package
does not depend on libx11 anymore.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
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>
Javier Viguera
Seth Bollinger
Hector Palacios
Alex Gonzalez