So the package can be compiled in a non-X11 graphical system.
https://jira.digi.com/browse/DEL-4289
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
* Disabled: dnsmasq and netconfig
* Enabled: cellular related options and connectivity check
https://jira.digi.com/browse/DEL-4289
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Avoid splitting the boot script message in two different lines:
Starting bluetooth hardware: [OK]
done.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
After 0e7f5d3a47 both platforms probe both ports,
which is problematic (for example, ttymxc4 is the console in the 6UL based
platforms).
Use more concrete rules to avoid that problem.
https://jira.digi.com/browse/DEL-4199
Signed-off-by: Diaz de Grenu, Jose <Jose.DiazdeGrenu@digi.com>off-by: Diaz de Grenu, Jose <Jose.DiazdeGrenu@digi.com>
After the kernel update (v3.14 to v4.1) the sysfs path changed from:
/devices/soc0/soc.0/2100000.aips-bus/21f4000.serial/tty/ttymxc4
to:
/devices/soc0/soc/2100000.aips-bus/21f4000.serial/tty/ttymxc4
which caused the XBee Cellular not to be detected on the new kernel. These more
general rules are compatible with both kernels.
https://jira.digi.com/browse/DEL-4199
Signed-off-by: Diaz de Grenu, Jose <Jose.DiazdeGrenu@digi.com>
mbedTLS is an open source, portable, easy to use, readable and flexible SSL
library.
https://jira.digi.com/browse/DEL-4101
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
QMI modems didn't work with the version of
modemmanager that the dey-2.2-r1 release was
using.
We were using two patches for uBlox plugin to use XBee Cellular 3G
that are now merged in modemmanager master.
This updates modemmanager to use the commit where QMI
problem was fixed and also include uBlox patches.
https://jira.digi.com/browse/DEL-4192
Signed-off-by: Salvador Penalva <salvador.penalva@digi.com>
Add patch to MM, so it detects the U-Blox modem connected to the XBee
socket.
https://jira.digi.com/browse/DEL-4084
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Tweaked to maintain some recipes' revisions to AUTOREV instead of the
fixed SHA1s from the tag.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The XBee Cellular needs more time to settle down before MM is able to
detect it on boot. As this is connected to one of the 'ttymxc' serial
ports, use that port to conditionally delay the launch of MM.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Adding more retries to the port AT probing has an impact in modems not
using serial drivers (for example using qmi, mbim). It takes longer for
MM to detect those modems and then user space gives up waiting for the
modems to be available.
This reverts commit 682d77e414.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The following changes have been made to the bluetooth-init script:
* Remove "hciconfig hci0 up/down" and this is now deprecated and likely
to fail. We use the AutoEnable feature of bluetoothd for this now.
* Move setting the MAC address to hciattach instead of using hcitool.
* Remove resets performed by hcitool and hciconfig. The hciattach
application already performs a reset and that should suffice.
* Remove hciattach retries.
https://jira.digi.com/browse/DEL-3711https://jira.digi.com/browse/DEL-3436https://jira.digi.com/browse/DEL-3636https://jira.digi.com/browse/DEL-3955
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This commits adds patches to hciattach for the following:
* Strict flow control setting
The hciattach application has a flow | noflow command line argument that is
currently only applied on the first configuration of the uart port. The
hciattach_rome plugin ignores this setting and assumes hardware flow
control is always supported. This commits makes hciattach obey the user flow
control indication.
* Modify hciattach_rome to set MAC address. The MAC address setting
feature in the rome plugin now works with the command line specified
MAC.
* Reduce verbosity. hciattach now accepts a "-v" verbose flag. By
default verbose output it omitted.
https://jira.digi.com/browse/DEL-3711https://jira.digi.com/browse/DEL-3436https://jira.digi.com/browse/DEL-3636https://jira.digi.com/browse/DEL-3955
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Launching the MM on target's boot fails to detect the XBee cellular
because this needs more time to complete the initialization. So add some
more retries for the AT port probing to allow the XBee cellular to be
detected.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Instead of redirecting the MM logging to '/dev/null' use a file, so we
can see what's going on in case of failure.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The flow control patches have been merged to the master branch, so
update the revision to remove those patches from our layer.
This reverts commit a7c51af5b8.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The XBee cellular support is at the moment only in modemmanager's git
repository (master branch).
Also remove one Telit patch from the bbappend because it's already
included in the git repo.
https://jira.digi.com/browse/DEL-3841
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This version of libqmi is needed for newer versions of ModemManager.
Remove bbappend and patch to previous version as the patch is now
included in the new version.
https://jira.digi.com/browse/DEL-3841
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The current script cannot launch the hostapd twice (for dual HostAP mode)
because start-stop-daemon finds an already existing PID for hostapd after
running the first instance.
The solution is:
- Do not launch the hostapd in background (so that it does not fork the
process, which assigns a different PID)
- Use -b option of start-stop-daemon so that it launches the daemon in
the background.
- Let start-stop-daemon create the PID (since the hostapd will not fork
now this PID will match the hostapd process, allowing to kill it later)
This solution also hides the hostapd log messages that appeared before.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-4045
The original init script hardcodes the configuration file to use so it
cannot be re-utilized for concurrent AP/AP mode where two interfaces can
be used as SoftAP.
This commit uses the variable ${IFACE} to:
- select a specific configuration file per interface:
/etc/hostapd_${IFACE}.conf
- create a specific PID file per interface:
/var/run/hostapd.${IFACE}.pid
With this, the /etc/network/interfaces can use the script for using SoftAP
in different wireless interfaces.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
- The Bluetooth daemon was always executed before setting up the
hardware, generating several problems specifically in the CCIMX6SBC.
This was causing the Bluetooth driver to override the Bluetooth name
and alias, as well as avoiding any host function on Bluetooth profiles.
Only pairing and ping was working, as well as client profile sides.
- This change also fixes some issues in the CCIMX6UL platforms with the
Bluetooth daemon failing to perform several bluetoothctl operations.
https://jira.digi.com/browse/DEL-4000https://jira.digi.com/browse/DEL-4015
Signed-off-by: David Escalona <david.escalona@digi.com>
The unlock retries feature from the Telit plugin does not work properly with
old versions of the Telit HE910 firmware. This has been fixed in upstream
commit: fbb607f0c25be3a4bb8692ee48445cf437345b6c
Signed-off-by: Salvador Penalva <salvador.penalva@digi.com>
https://jira.digi.com/browse/DEL-3863
This reverts commit 3123085e72.
we revert this commit because the patch was already applied on mm-1.6.4
Signed-off-by: Salvador Penalva <salvador.penalva@digi.com>
Reviewing the patches while updating the QCA firmware to a new release,
I encountered this patch. On the original PR it says:
"Do not use hcitattach to reconfigure the baudrate but set it directly in the
Bluetooth FW file; this save us from some syncronism problems if we are not
using HW flow control."
Current spins of the module already use hw flow control. Also, not allowing
hciattach to override the baudrate does not seem right to me. It would be
enough with passing a 3M baudrate to hciattach to match the firmware
default.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This commit fixes an issue with ModemManager to return the correct
error code when an invalid QMI command is send to the modem.
There are two ways to get the UIM/SIM status, one with the "DMS"
service that works on most devices from 2015 and earlier, and a
new way with the "UIM" service that works on many 2015+ devices.
Perhaps the EC21 is new enough that it requires the UIM service,
but ModemManager doesn't recognize the error code that it's returning.
There are two ways to get the UIM/SIM status, one with the "DMS"
service that works on most devices from 2015 and earlier, and a
new way with the "UIM" service that works on many 2015+ devices.
Perhaps the EC21 is new enough that it requires the UIM service,
but ModemManager doesn't recognize the error code that it's returning.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-3748
This commit fixes an issue with the Quectel EC21/EC25 due to a wrong
reported DMS version which will cause ModemManager not to read the
SIM card.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-3748
Implement:
* support to start, stop and restart interface
* states machine and retries system to recover from command failures
* overall simplification and code clean-up
https://jira.digi.com/browse/DEL-3858
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
With the upgrade to Morty, there is a new bootscript that is provided
by Poky. This bootscript is just launching the generic bluetooth daemon,
but it's not doing any hardware initialization.
The fix is to split the hardware initialization to a different
bootscript 'bluetooth-init' and launch it also on boot.
https://jira.digi.com/browse/DEL-3855
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
If you try to use libmbim (the API is used at least by mbim-network,
mbimcli and ModemManager applications) you get the following error:
ModemManager: Error converting string: Conversion from character
set 'utf-8' to 'utf-16le' is not supported
In order to solve this we need to integrate glibc gconv UTF16le library
in the build (and its dependencies).
Signed-off-by: Mike Engel Mike.Engel@digi.comhttps://jira.digi.com/browse/DEL-3830
This commit adds the wireless concurrent mode as a default
configuration to the CC6UL machine.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-3818
There is now a WLAN user guide with configuration examples so there is
no need to pollute the default file with comments.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The LICENSE is added through the packagegroup bbclass and the checksums
were outdated making the build fail with:
The LIC_FILES_CHKSUM does not match for poky/LICENSE;md5=3f40d7994397109285ec7b81fdeb3b58
https://jira.digi.com/browse/DEL-3451
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The wireless regulatory database has been moved to its own recipe, so
the update cannot be done bbappending this recipe.
This reverts commit 8e69db8ac5.
https://jira.digi.com/browse/DEL-3451
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This parameter allows to set the time interval for scheduled scans in
seconds. This is usually managed by the wpa-supplicant dynamically, but
for example with DFS channels and non broadcasting SSIDs re-associations
take too long if the periodic scans time interval is not reduced.
https://jira.digi.com/browse/CC6UL-594
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This commit adds a wpa supplicant P2P configuration file and configures
the p2p0 interface automatically at pre-up.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Optimize the provided config file with default support for 802.11ac.
https://jira.digi.com/browse/DEL-3128
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Do not use hcitattach to reconfigure the baudrate but set it directly in the
Bluetooth FW file; this work arounds some synchronization problems when not
using HW flow control.
https://jira.digi.com/browse/DEL-3052https://jira.digi.com/browse/DEL-3057
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Copy of the original defconfig in hostapd-2.4 and enabling next options:
- CONFIG_LIBNL32
- CONFIG_EAP_PSK
- CONFIG_EAP_PWD
- CONFIG_WPS
- CONFIG_WPS_NFC
- CONFIG_RADIUS_SERVER
- CONFIG_IEEE80211N
- CONFIG_IEEE80211AC
- CONFIG_DEBUG_FILE
This means that the hostapd binary will have support for that features, but it
does not imply that the wireless chip does support it.
https://jira.digi.com/browse/DEL-2936
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Do not autostart hostapd daemon on boot because because it will conflict with
wpa-supplicant process and add a custom hostapd.conf file with WPA2-AES
encryption.
https://jira.digi.com/browse/DEL-2913
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
We need a different configuration file, because the SoftAP functionality is
supported using the hostapd package instead of the wpa_supplicant.
https://jira.digi.com/browse/DEL-2744
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Add a couple of bluez patches: one for increasing the number of connection
showed with "hcitool con" command and remove "refresh" option in hcitool
help that is not supported.
The qca6564 chip can support more than 10 simultaneous BLE connections.
https://jira.digi.com/browse/DEL-2735
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
The power regulator connected to the qca6554 chip is always on, which causes
the Bluetooth part to not work correctly after a software-reset.
This commit asserts momentarily the BT_EN line during the start-up sequence
to reset the Bluetooth controller so that it is in a predictable state after a
reset.
https://jira.digi.com/browse/DEL-2623
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
This function is deprecated in favor of bb.utils.contains. The same
change has been done in other layers.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The steps to set the bluetooth MAC address is send an specific hci command
and an hci reset, so the bluetooth interface need to be up in order to
configure it.
Additionally we have generalized the way to read the MAC address from the
device tree and removed some old code for getting the MAC address in
kernel version 2.
https://jira.digi.com/browse/DUB-595
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Add a software workaround to disable the HW flow control because the SOM
revision 3 (and older) has swapped the bluetooth TX and RX lines so we need
to operate in DTE mode which implies that the HW control lines are swapped.
This also implies reducing the baudrate to avoid the need for HW flow control.
https://jira.digi.com/browse/DEL-2611
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Port the bluez5 qca6564 support based on 5.19 to the current version 5.33.
The ported version is based on qualcomm tag r110048.3.
https://jira.digi.com/browse/DEL-2581
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
As of Yocto 2.0, the cryptodev module used as interface between
user-space and hardware encryption is the version 1.7.
According to that cryptodev's version documentation, the cryptodev
engine in openssh is outdated:
https://github.com/cryptodev-linux/cryptodev-linux/blob/cryptodev-linux-1.7/README
They provide an URL with two patches to update openssl. This commit
forward port those patches to the Openssl version used in this version
of Yocto.
https://jira.digi.com/browse/DEL-2501
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This install the 'obexd' server which is needed for the QT5 bluetooth
file transfer example applications.
https://jira.digi.com/browse/DEL-2147
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The script toggles the BT power GPIO regardless of the value being
undefined.
Check that the GPIO is defined before trying to toggle it.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
The BT power GPIOgpio was determined basing on machine name on device tree.
This corresponds to the name of the board, and might be changed by a user
that designs his own carrier board to use the module on.
Besides, the BT power GPIO is a pin that's routed on the module (both on
the ConnectCore 6 and on the ConnectCard for i.MX28) not on the carrier
board.
This commit determines the BT power GPIO basing on the module string inside
the 'compatible' property. This must exactly match the module name and is
a required property for using Digi module's BSP.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-2109
The autotools class is trying to execute:
intltoolize --copy --force --automake
so there is a intltool-native dependency.
Fix:
run.do_configure: intltoolize: not found
ERROR: Function failed: do_configure
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Add BLUEZ5_NOINST_TOOLS to bluetooth packagegroup. Gatttool is
added to BLUEZ5_NOINST_TOOLS in bluez5.inc so it is not necessary
to add gatttooll to do_install_append function.
Signed-off-by: Urko Nalda <Urko.Nalda@digi.com>
Add support for bluez5 profiles under experimental flag.
Health Device Profile is an experimental profile.
https://jira.digi.com/browse/DEL-1936
Signed-off-by: Urko Nalda <Urko.Nalda@digi.com>
If the bluetoothd daemon is launched before the interface is ready
RFCOMM/L2CAP listening socket connections fail (apparently because
the channel is not ready) with BlueZ 5.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-2042
yocto-2.0 (jethro) does not support bluez4 by default, it has been set
deprecated, but there is some functionality that does not work with bluez5
like bluetooth audio with alsa and some previous scripts like hdp.py are not
API compatible.
In order to compile a project with bluez4, just remove bluez5 from distro
features from your local.conf project.
DISTRO_FEATURES_remove = "bluez5"
https://jira.digi.com/browse/DEL-1943https://jira.digi.com/browse/DEL-995
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Do not include the btfilter support in the default images. Its support is
not required for bluetooth functionality.
https://jira.digi.com/browse/DEL-1935
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
btfilter (abtfilt) and bluetoothd are two independent services. Break the
relationship between them and split the support in independent init scripts
https://jira.digi.com/browse/DEL-1933
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
The script was basing on the variant coded in the HWID to determine
if the variant had bluetooth, by comparing to an array of hard-coded variants.
This required the script to be updated with every new variant that supported
Bluetooth.
The patch checks instead if the node 'bluetooth' exists at all in the device tree
to determine if the variant supports Bluetooth.
https://jira.digi.com/browse/DEL-1933
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
We want to unlink the script from abtfilt application, so moved to a different
recipe (that includes hciattach).
https://jira.digi.com/browse/DEL-1933
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
The problem is the change of the default C standard from gnu89 to gnu11
which changes the semantics of 'inline'. The issue is described in the
porting guide at https://gcc.gnu.org/gcc-5/porting_to.html.
Fix based on u-boot's commit dfc9c24
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
ccimx51js and ccimx53js are not supported in this version of DEY.
Support for those platforms is in previous versions of DEY.
https://jira.digi.com/browse/DEL-1890
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This is an atheros proprietary package that contains the athtestcmd and
wmiconfig applications.
Neither of them are currently used.
https://jira.digi.com/browse/DEL-1878
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Which wireless module to use belongs more to the machine config files in
the BSP layer, than to the generic wireless packagegroup.
https://jira.digi.com/browse/DEL-1858
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The external kernel module does not build with linux 3.14, and we want
to test the upstream driver included in the kernel tree.
So for the moment disable the external kernel module, to allow start
building images in the buildserver.
https://jira.digi.com/browse/DEL-1748
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Add the following lines to add support for the HSP/HFP and A2DP profiles,
and to route the audio through the HCI SCO channel:
Enable=Source,Sink,Headset,Gateway,Control,Socket,Media
SCORouting=HCI
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Remove the patch because it's now included in wpa_supplicant v2.3
https://jira.digi.com/browse/DEL-1558
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
It has never been a mirror of upstream packages.
It's the URL of packages needed for the BSP. These packages are mostly
Digi specific and not provided in any other location.
https://jira.digi.com/browse/DEL-1493
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit d4cf9a88c9db39c6ecfd0099437d82af81c96e85)
https://jira.digi.com/browse/DEL-1359
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit 537803cb64809acbac243179d6d448ad6cd70b85)
This installs 'libbluetooth.a' in the toolchain (needed to build static
binaries that use libbluetooth).
https://jira.digi.com/browse/DEL-1303
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit f53ae4ab2af1bc5dd2f3f38f9d351d9eefd1f163)
gobject introspection is not supported in Yocto, so there is not a
python binding package to use it.
Bluez4 uses such functionality in some of the test scripts. This patch
replaces it with the legacy pygobject, so they can work again.
https://jira.digi.com/browse/DEL-1274
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The bbappend was created mostly to install an old version of the
'simple-agent' test application (the one included in the package was
failing) but upstream (Poky) has fixed most of the issues, so our
bbappend is just needed now to enable 'health' profile support.
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>
'/run/vsftpd/empty' directory is created at runtime via volatiles
bootscript under /run TMPFS.
Workaround error:
ERROR: QA Issue: vsftpd: Files/directories were installed but not shipped
/run
/run/vsftpd
/run/vsftpd/empty
ERROR: QA run found fatal errors. Please consider fixing them.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Add the machine specific files for the ccimx6adpt platform. Initially
they are copied form the ccardimx28js as it is also planned to use
an Atheros chipset.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
wpa_supplicant v2.0 was not available in Danny so we needed the whole
recipe, but it was updated in Dylan, so now we just need the bbappend.
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>
'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 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>
Modify the atheros and bluetooth init scripts to fetch the hwid details
from the device tree.
https://jira.digi.com/browse/DEL-572
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>
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>
The MACHINE_ESSENTIAL_EXTRA_* vars need to be only in the
'packagegroup-dey-core' recipe not in the rest of the packagegroups.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
QA Issue: Variable ALLOW_EMPTY is set as not being package specific
QA Issue: Variable RPROVIDES is set as not being package specific
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The 3.10 kernel uses the upstream atheros driver.
Also, rationalize the RDEPENDS in the recipe to use the wireless
module variable instead of hardcoding values.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The official cherokee project page has repacked the source and broken
backwards compatibility. They also erase old images when new ones are
released.
This commit changes the download location to a mirror with the original
tarball that also keeps the archives.
https://jira.digi.com/browse/DEL-516
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
They removed old versions from the download location so 4.54 now fails.
https://jira.digi.com/browse/DEL-516
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The final product will be called "Digi Embedded for Yocto" or DEY for
short.
This commit renames all relevant files.
https://jira.digi.com/browse/DEL-474
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Mike Engel
Javier Viguera
Diaz de Grenu, Jose
Tatiana Leon
Salvador Penalva
Alex Gonzalez
Hector Palacios
David Escalona
Isaac Hermida
Urko Nalda
Jose Diaz de Grenu de Pedro