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>
In order to build tiny or tiny-initramfs images, the script adds
the line:
DISTRO_FEATURES_remove = "x11"
to 'conf/local.conf' file.
https://jira.digi.com/browse/DEL-2106
Signed-off-by: Urko Nalda <Urko.Nalda@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>
After the merge of the kernel's stability patches, the driver
uses the include for Freescale BSP beyond 3.14.28.
Despite having applied the kernel stability patches and having
a kernel version beyond 3.14.28, we still use Freescale's BSP
for 3.14.28, so let's keep the busfreq include for any 3.14.x
version.
This patch may need to be reverted if the BSP is moved to a
newer one by Freescale.
Signed-off-by: Hector Palacios <hector.palacios@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>
ARCH is not a documented variable in yocto, use the documented
TARGET_ARCH instead.
https://jira.digi.com/browse/DEL-2032
Signed-off-by: Jose Diaz de Grenu de Pedro <Jose.DiazdeGrenudePedro@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>
This commit adds the minimum GPU frequency patch to the community
Vivante GPU driver repository.
https://jira.digi.com/browse/DEL-1969
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This is needed when you use a PREMIRROR (as we usually do in buildserver
builds). Otherwise there is a strange corner case where the do_fetch
task fails when the upstream git repo has been rebased and the old mirror
tarball does not have the new SHA1 revision.
ERROR: Function failed: Fetcher failure for URL: 'git://git.yoctoproject.org/matchbox-window-manager'. Unable to fetch URL from any source.
Signed-off-by: Javier Viguera <javier.viguera@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
Urko Nalda
Hector Palacios
Alex Gonzalez
Jose Diaz de Grenu de Pedro
Isaac Hermida