The recipe modifies the Greengrass Core init script to properly configure the
daemon relative path. This daemon location is different depending on the
Greengrass version being used.
This commits also moves the patch for Greengrass Core 1.0.0 to the
'greengrass-1.0.0' directory in preparation for adding Greengrass Core 1.1.0
recipe in the next commit.
https://jira.digi.com/browse/DEL-5368
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
This commit updates dnsmasq to version 2.78 to include the following
vulnerability patches:
* CVE-2017-13704
* CVE-2017-14491
* CVE-2017-14492
* CVE-2017-14493
* CVE-2017-14494
* CVE-2017-14495
* CVE-2017-14496
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-5136
The current recipe copies binaries for different ARM architectures to
the rootfs.
For the CC6UL we need to save some space, so delete the versions of the
binaries that are not being used.
https://jira.digi.com/browse/DEL-4987
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The current recipe copies binaries for different ARM architectures to
the rootfs.
For the CC6UL we need to save some space, so delete the versions of the
binaries that are not being used.
https://jira.digi.com/browse/DEL-4987
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This allows to specify a different set of gstreamer packages to be
installed per machine. It's mainly used for the CC6UL to define a
minimum set of packages that allows to play a WEBM video, and at the
same time save some space as this platform does not have much storage.
The space saved with this change for the CC6UL and the default QT image
is about ~5MB.
https://jira.digi.com/browse/DEL-4987
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
virtwlans script creates an additional interface on startup for QCA6564 chip.
The created interface purpose is for ap mode, so specify its type on creation.
https://jira.digi.com/browse/DEL-5290
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
This creates a new dispatcher action DEVICE_CONNECTIVITY_CHANGE, that
gets triggered whenever one interface fails in the upstream connectivity
check, regardless of the system having connectivity through a different
interface.
https://jira.digi.com/browse/DEL-5210
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Subset of commits to fix the pairing for dual mode devices. Main
commit that fixes is 2d3685252a21cda4b918ad1cc4dd0572bd5c6d3c, but some
previous commits are required as well.
"""
For dual mode devices we need to pass address type used in pairing
events to reply with correct one on agent reply. Otherwise reply for
BR/EDR pairing of dual mode device would use address type (which is
valid only for LE address) resulting in reply being ignored by kernel
and eventually pairing timeout.
"""
https://jira.digi.com/browse/DEL-5226
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
For avoid compilation error due to platform specific patches, first apply
the common patches and later apply platform specific patches.
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Create a multiple patch file with the original qualcomm code that adds
support for the qca6564 chip (hcitattach_rome)
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
This commit re-adds the imx-gpu-g2d recipe that was removed
from the imx-gpu-viv v6 driver.
https://jira.digi.com/browse/DEL-5234
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This commit adds a platform dependency to remove the parts
provided by the new GPU driver and maintain the compatibility
for other platforms using previous versions.
https://jira.digi.com/browse/DEL-5234
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This commit adds the recipe to update the GPU driver
to the latest version.
https://jira.digi.com/browse/DEL-5234
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The XBee Cellular modem is expected to be at ttymxc1 on CC6UL and
at ttymxc4 on CC6. The changes are needed because in v4.9.11 kernel
the /sys/devices entry for CC6UL and CC6 are the same for the TTYs,
causing that on CC6UL ModemManager was also searching for modems on
ttymxc4.
Signed-off-by: Sebastian Pastor <sebastian.pastor@digi.com>
https://jira.digi.com/browse/DEL-5163
This commit modifies different recipes to support the new platform
ccimx6qpsbc and adapt it to maintain the support to ccimx6sbc.
https://jira.digi.com/browse/DEL-5082
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This commit modifies sysinfo tool to use the kernel symlinks for
the devices instead of using the full node path and maintain
compatibility with different kernel versions.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The experimental flag is needed to run the GATT server application.
https://jira.digi.com/browse/DEL-5023
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
These examples show how to use the Digi APIX.
https://jira.digi.com/browse/DEL-5097
Signed-off-by: Francisco Gil Martinez <francisco.gilmartinez@digi.com>
This commit adds the some platform board files and removes
the symbolic link to libsoc.conf
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-5096
This commit enables the IPV6 support that is necessary for the
XBee Cellular LTE Cat1 modem.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-4839
This commit creates a new file called 'dey-version-${REAL_MULTIMACH_TARGET_SYS}'
(for example, 'dey-version-cortexa7hf-neon-dey-linux-gnueabi') at the same level
as 'version-${REAL_MULTIMACH_TARGET_SYS}',
'site-config-${REAL_MULTIMACH_TARGET_SYS}', and
'environment-setup-${REAL_MULTIMACH_TARGET_SYS}' files.
The file contains the following parameters:
* Machine. The name of the platform the toolchain was built for (ccimx6sbc,
ccimx6ulsbc, ccimx6ulstarter).
* Version: A versioning system for the generated toolchains. Currently is the
distro version followed by the timestamp on which the current build started.
* Image: The name of the image that triggered the population of the SDK
(core-image-base, dey-image-aws, dey-image-qt-${GRAPHICAL_BACKEND})
The purpose of the 'dey-version-*' file is to be parsed by Eclipse so toolchains
can be autodetected.
This file is packaged with the rest of SDK/toolchain resources ('version-*',
'site-config-*', and 'environment-setup-*' files, and 'sysroots' directory)
when creating the SDK tarball and later the installation script.
The 'dey-version-*' file could also be created in a 'meta-environment.bbappend'
appending to the 'create_sdk_files()'. But from this recipe there is no access
to the name of the image that triggers the creation of the SDK (core-image-base,
dey-image-aws, dey-image-qt, etc.).
Currently, we are redefining 'SDK_POSTPROCESS_COMMAND' (from
'poky/meta/classes/populate_sdk_base.bbclass') to insert the generation of the
'dey-version-*' file just before creating the SDK tarball.
https://jira.digi.com/browse/DEL-5074
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
NM launches 'dnsmasq' using DBus, so enable DBus support at compile
time. Also remove the symlinks in the different runlevels, so it's not
launched by the included bootscript.
https://jira.digi.com/browse/DEL-4787
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This is needed in the context of network failover, so when one physical
interface is lost, you can still resolve the connectivity-check URL
using the local DNS cache.
https://jira.digi.com/browse/DEL-4787
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The implemented patch fails when NetworkManager uses a local DNS cache
underneath (like 'dnsmasq'). To access the local DNS cache it needs to
use the loopback interface and hardcoding the physical interfaces make
the connectivity check fail.
This reverts commit c9b02d6288.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Use the same interface that it's being checked for the DNS resolution.
This makes connectivity check work in an scenario where the primary
interface has lost connectivity (for example ethernet) but you still
have connectivity through a secondary interface (e.g. wireless).
What happens in that case is that even though you have correct
connectivity in the secondary interface the check fails because it does
not use that secondary interface to resolve the name of the test URL.
The result is that the connectivity check assumes that this secondary
interface is also failing and it penalizes the metrics in the routing
table.
This commit uses libcurl's CURLOPT_DNS_INTERFACE to set the DNS
interface. Notice that this requires 'libcurl' to be compiled with
'--enable-ares'.
https://jira.digi.com/browse/DEL-4787
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This is required to use '--dns-interface' runtime parameter to instruct
'curl' to use a specific interface for DNS resolution.
We need this in the context of the network failover support, where
NetworkManager does the connectivity check, by trying to connect to a
configured URL through the different interfaces available, and for this
check it uses 'libcurl' underneath.
If you try to use this functionality without this build time option
enabled, you get:
curl: (4) A requested feature, protocol or option was not found built-in
in this libcurl due to a build-time decision.
https://jira.digi.com/browse/DEL-4787
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Arturo Buzarra
Francisco Gil
Tatiana Leon
Mike Engel
Javier Viguera
Isaac Hermida
Jose Diaz de Grenu
Sebastian Pastor
David Escalona