I have split the machine configuration in two:
-The module machine configuration include, for example ccimx53.inc
-The machine configuration (for example cimx53js.conf) which includes
the variant configuration.
This will allow for customers to create their own machine keeping the
module include file.
The variant can be configured in the local.conf file with a
MACHINE_VARIANT variable.
The variant names are made up of the interface initials as follows:
w: wifi
e: externel ethernel
b: bluetooth
1: 1-wire
a: accelerometer
g: GPU
v: VPU
128: 128MB RAM
4k: 1024MB NAND (only for MX51 JTAG flash)
For details regarding the supported variants, each machine configuration
file contains a comment with a variants table.
https://jira.digi.com/browse/DEL-330
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
* don't use a login shell to run the script. It overrides the
environment that comes from the caller script.
* optimize MAC address parsing
* enable 'P2P' and softmac on driver's load
https://jira.digi.com/browse/DEL-412
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This version of the driver can be redistributed, so remove the
build-from-objects part of the recipes.
https://jira.digi.com/browse/DEL-412
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
They all have a copyright and the all do:
PR = "${DISTRO}.${INC_PR}.0"
Then recipes which include them include:
PR = "${DISTRO}.${INC_PR}.0"
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
All bbappend files will start as follows:
# Copyright (C) 2013 Digi International.
PRINC := "${@int(PRINC) + 1}"
PR_append = "+${DISTRO}"
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
On a release, the kernel will not be built from a git repo but
from a source tarball.
Make the default to build from a tarball.
https://jira.digi.com/browse/DEL-362
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Not yet finished as not all the cpx2 variants support wireless.
This has to be enabled per-variant.
https://jira.digi.com/browse/DEL-134
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This was causing module loading issues on del-image-graphical.
Fixes https://jira.digi.com/browse/DEL-338
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Following the guidelines in kernel documentation:
linux-tree/Documentation/kbuild/modules.txt
https://jira.digi.com/browse/DEL-134
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Create a symlink on the deploy folder that matches the standard uboot
name for the kernel.
Fixes partially https://jira.digi.com/browse/DEL-283
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
udev will attempt to load the atheros kernel modules because it defines
a modalias that matches an sdio bus event.
In a race condition with the script in if-pre-up, the module will crash.
Recent versions of udev have lost the ability to add an ignore_device
option to the rules, and mdev in del-image-minimal has no module
autoloading ability.
The commit adds a modprobe install rule that does nothing, and allows
the if-pre-up script to load the module as it used to.
Fixes https://jira.digi.com/browse/DEL-277
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The del-examples-sahara now depends on the kernel modules it needs to
work and these are autoloaded at boot.
Fixes DEL-274.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
For this the CCIMX51 and CCIMX53 kernels are configured to build the
mma7455l module and it is included as a dependency of the del-examples-
accelerometer application.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This conflicts with user led 2 used in the GPIO example add and with
other interfaces needed in the del-image-graphical image.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Wakeup interrupts were not happening upon USB stick plug
events during normal work. This had the effect of the
interrupt happenign when going to suspend and usually when
the driver is not able to handle it, causing a nobody cared
message from the kernel.
https://jira.digi.com/browse/CCIMX28-326
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
Just a cosmetic name change for the merged wired and wireless platforms.
This and related commits fixes https://jira.digi.com/browse/DEL-188.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Also enable CONFIG_BRIDGE in kernel configs (which is required to use
brctl)
https://jira.digi.com/browse/DEL-156 #resolve
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Enable RFKILL. Otherwise on boot we get an error message:
rfkill: Cannot open RFKILL control device
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
We need the kernel configuration file in /boot for some of the postint
scripts that aim to do smart things like autoconfigure the interfaces file.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The bootloader is passing the mac address and wdmode in the kernel command
line.
The driver startup script reads and and sets them.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The bootloader is passing the mac address in the kernel command line.
The driver startup script reads it and sets it.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
These new defconfigs are needed after merging the wireless and non wireless
products in the linux kernel source.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
We need to split the EXTRA_OEMAKE flags as the do_make_scripts stage
fails if we pass a "M=" argument.
We override module_do_compile and module_do_install to add the extra
make flags as I have not found a working way of overriding EXTRA_OEMAKE.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This included the recipe where the driver is cloned from git and compiled
from source.
The recipe also copies the firmware files and the if-pre-up scrip.
Pending is the recipe to link from precompiled objects in a .tar.gz file.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This is the same as the meta-fsl-arm layer and allows for more recipes
for different kernel versions to be considered.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>