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>
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>
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 public branches of those repositories have been cleaned up so
the external sha1s have changed.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Another option would be to split it up in machine folders, but it is
similar enough in all platforms not to need this for the time being.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Fix the kernel wireless configuration fragment, and add a couple of kernel
patches to set up the mmc0 interface to be used with the wireless and
remove an incorrect pin configuration.
There are similar patched to this on the gateways/master branch related to
the vehicle bus adapter product.
meta-digi-arm/conf/machine/cpx2.conf
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This manually reverts commit ecfdf6ae23.
Once mdev was removed as a dependency from del-image-graphical, we need
udev to load the firmware files for the wireless drivers. This job was
being done by mdev.
The reason for the commit in the first place was that both mdev and udev
were attempting to load the firmware files, so we changed the udev
rule to ignore the atheros driver. This was only needed when mdev and
udev were both running.
https://jira.digi.com/browse/DEL-450https://jira.digi.com/browse/DEL-450
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>
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>
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>
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>
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>
Javier Viguera
Alex Gonzalez