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>
Javier Viguera
Robert Hodaszi
Alex Gonzalez