The example applications are not packaged by default, so extend the
recipe to create a package with the example applications.
https://jira.digi.com/browse/DEL-1960
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
So we can build a 'dey-image-graphical' image for framebuffer with
support for QT5.
https://jira.digi.com/browse/DEL-2017
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
No functional change, as 'package-management' is added via the included
dey-image-minimal recipe, and 'pointercal-xinput' is a dependence of
xinput-calibrator which is added for X11 images.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
By default QT5 applications use 'xcb' platform plugin but this can be
changed using the QT_QPA_PLATFORM environment variable. On non-X11
images the 'xcb' platform plugin obviously does not work, so just
configure 'eglfs' for non-X11 images.
https://jira.digi.com/browse/DEL-2017
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
There are some demo apps that otherwise fail with:
QSqlDatabase: QSQLITE driver not loaded
QSqlDatabase: available drivers:
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This demo app is very generic and does not play well with FSL gstreamer
plugin, so using it just crashes in different ways (doing a camera zoom,
recording a video, etc)
This reverts commit 2776dcd654.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
We will use 'qmlvideo' application for QT5 media player demo, so just
create a desktop launcher.
https://jira.digi.com/browse/DEL-2007
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
These demo applications are only distributed in binary form. We don't
have the source code as an example for customers, so just remove them.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The aim is to reduce even more the memory used by the host at build time
to avoid the OOM killer killing the linker.
Otherwise it can fail in machines with few memory even though the linker
is configured with '--no-keep-memory'.
Notice that we also reduce the parallel jobs expanded by 'ninja' build
system configuring and exporting NINJAFLAGS variable. Otherwise this
build system does not honor PARALLEL_MAKE variable.
Fix:
arm-dey-linux-gnueabi-g++: internal compiler error: Killed (program cc1plus)
ninja: build stopped: subcommand failed.
https://jira.digi.com/browse/DEL-1973
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
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>
The meta-qt5 layer provides a 'populate_sdk_qt5' class with all what's
needed to build a SDK based on an image recipe.
Inherit the class here so it's available for all DEY image recipes
depending on 'dey-qt' image feature.
https://jira.digi.com/browse/DEL-1973
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This distro feature adds a lot of dependences when building a
toolchain/SDK (maininly all the *-ptest packages but some more). One of
those dependences fails when building the toolchain:
warning: Removing procps-3.3.10-r0.1@cortexa9hf_vfp_neon due to file /etc/sysctl.conf conflicting with base-files-3.0.14-r89.1@ccimx6sbc
error: procps-dev-3.3.10-r0.1 requires procps = 3.3.10-r0.1
There is no functionality loss because the 'ptest' packages are just a
sort of unit testing script for each package, and we are not testing all
the open source and third party packages.
https://jira.digi.com/browse/DEL-1973
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>
Adding these demo apps allows to install the base QT libs as well,
because they are resolved automatically by bitbake.
https://jira.digi.com/browse/DEL-1972
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This is copied verbatim from the 'meta-fsl-bsp-release' layer. FSL
distributes these applications in binary-only form.
https://jira.digi.com/browse/DEL-1972
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Otherwise at run time there is no service available that is able to
manage the multimedia files and there is a failure:
requestService(): no service found for - "org.qt-project.qt.camera"
requestService(): no service found for - "org.qt-project.qt.mediaplayer"
https://jira.digi.com/browse/DEL-1972
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
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>
Javier Viguera
Hector Palacios
Urko Nalda
Alex Gonzalez
Jose Diaz de Grenu de Pedro
Isaac Hermida