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>
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>
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>
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>
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>
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>
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>
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
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
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>
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>
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>
Javier Viguera
Alex Gonzalez
Hector Palacios
Seth Bollinger