This is a build-time option, nothing to do with runtime. Decrease the
memory used by the linker to avoid being killed due to out-of-memory.
https://jira.digi.com/browse/DEL-1972
Signed-off-by: Javier Viguera <javier.viguera@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
We switch to the way it works in Android, short press (<2s) takes the target
to suspend and long press, >2s but <9s, performs a software controlled
power down.
Pressing longer than 9 seconds does the uncontrolled hardware power off
directly from the PMIC.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Patches from 'meta-fsl-bsp-release' branch 'fido_3.14.38_6UL_patch'.
https://jira.digi.com/browse/DEL-1992
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Patches from 'meta-fsl-bsp-release' branch 'fido_3.14.38_6UL_patch'.
https://jira.digi.com/browse/DEL-1992
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Patches from 'meta-fsl-bsp-release' branch 'fido_3.14.38_6UL_patch'.
https://jira.digi.com/browse/DEL-1992
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Patches from 'meta-fsl-bsp-release' branch 'fido_3.14.38_6UL_patch'.
https://jira.digi.com/browse/DEL-1992
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The suspend script did a ifup/ifdown on wlan0 to workaround issues we
had using wireless drivers on some platforms.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
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>
Now that the MX5 platforms have been removed the only value for
WPA_DRIVER is 'nl80211' (used by Atheros wireless driver), so there is
no need to have a platform specific value.
Just initialize the value in the init-ifupdown recipe with a weak
assignment so it can be override from the project's local.conf.
https://jira.digi.com/browse/DEL-1890https://jira.digi.com/browse/DEL-1969
Signed-off-by: Javier Viguera <javier.viguera@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>
It has a hard-coded dependence in bluez4 and this has been removed from
openembedded-core.
There is a different Jira for the bluez5 migration.
https://jira.digi.com/browse/DEL-1890
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Also remove QT4 phonon patches and qtmediaplayer demo as they depend on
gstreamer-0.10.
https://jira.digi.com/browse/DEL-1890
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This reverts commit f7e2e8bd2c.
FSL has updated this package to version v4.0.7 in meta-fsl-arm.
https://jira.digi.com/browse/DEL-1890
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This reverts commit d4fb6a238e.
The patch we were backporting to alsa-utils 1.0.28 is included in
alsa-utils 1.0.29 (which is used in Yocto 2.0).
https://jira.digi.com/browse/DEL-1890
Signed-off-by: Javier Viguera <javier.viguera@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>
The mutex locking was not well resolved and a basic pipeline like:
gst-launch-1.0 playbin uri=file:///run/media/mmcblk0p5/big_buck_bunny_480p_h264.mov
was failing with:
Attempt to unlock mutex that was not locked
https://jira.digi.com/browse/DEL-1850
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The FSL gstreamer-0.10 plugin has renamed the video sink from
'mfw_v4lsink' to 'imxv4l2sink' so the phonon patches need to be updated
accordingly.
https://jira.digi.com/browse/DEL-1850
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>
Microcom is a minimal version of minicom and is extremely useful
for doing basic testing on target (for instance, talking to a modem
or other serial connected device).
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
(cherry picked from commit 90c6708e948c9b9942b48d425ff21e0affc2f8d7)
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
In yocto 1.8 if the BUILDNAME is empty, it gets filled with a timestamp
during the build. However the value and format of this timestamp are
different from the ones used in the name of the image.
This change matches the formats and values, setting the value of BUILDNAME
to the timestamp used in the name of the image.
Signed-off-by: Jose Diaz de Grenu de Pedro <Jose.DiazdeGrenudePedro@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>
Duration (-d) option was broken.
cherry pick from 8f361d83cfcb39887f5fc591633e68d9448e3425.
https://jira.digi.com/browse/DEL-1828
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
There is only one kernel supported for each platform, so there is no
need to explicitly set the kernel preferred version.
Also:
* Remove IS_KERNEL_2X variable which is no longer needed.
* Simplify jenkins build script, now that we do not need to build two
kernel versions for ccardimx28.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Add the networking configuration to support the creation of a bridge
interface.
Signed-off-by: Jose Diaz de Grenu de Pedro Jose.DiazdeGrenudePedro@digi.com
Javier Viguera
Hector Palacios
Alex Gonzalez
Jose Diaz de Grenu de Pedro
Isaac Hermida
Paul Osborne