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>
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
This was used just for SARES testing and according to the SA team it is
not needed anymore, so just remove it.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
dependences for consistency
The GPIO and ADC examples are not meant for the mx6 familiy, so make their
dependences platform dependent
Signed-off-by: Jose Diaz de Grenu de Pedro <Jose.DiazdeGrenudePedro@digi.com>
https://jira.digi.com/browse/DEL-1698
Signed-off-by: Jose Diaz de Grenu de Pedro <Jose.DiazdeGrenudePedro@digi.com>
(cherry picked from commit 42997de56cf3f3943518e782332effad66965b21)
Conflicts:
meta-digi-dey/recipes-digi/dey-examples/dey-examples-bt.bb
meta-digi-dey/recipes-digi/dey-examples/dey-examples-btconfig.bb
meta-digi-dey/recipes-digi/dey-examples/dey-examples-can.bb
meta-digi-dey/recipes-digi/dey-examples/dey-examples-hdp.bb
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>
Now each platform is only supported in one kernel version, so there is
no need to have multiple calib files per linux kernel version.
https://jira.digi.com/browse/DEL-1747
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>
Those packages are not machine specific, so there is no need to set
PACKAGE_ARCH to ${MACHINE_ARCH}.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This simplifies the code and as an extra allows to override the default
root password from the project's local.conf (setting MD5_ROOT_PASSWD
variable)
https://jira.digi.com/browse/DEL-1558
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Poky added a new class that provides the same functionality we
implemented in our 'dey-image' class. So just use that class instead
of reimplementing it in our layer.
https://jira.digi.com/browse/DEL-1558
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Remove 'dey-test' image feature and create a SARES bbclass with the
same functionality. This makes easier the creation of images suitable
for SARES testing just adding:
INHERIT += "sares-image"
to your project's local.conf
https://jira.digi.com/browse/DEL-1558
Signed-off-by: Javier Viguera <javier.viguera@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>
Now it depends on the last set capture mode which may be not compatible.
https://jira.digi.com/browse/DEL-1521
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Changes in Poky (Dizzy) made our SDK unable to build QT applications.
This commit syncs again with upstream so the toolchain is able to build
QT apps.
https://jira.digi.com/browse/DEL-1544
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Add a Digi mirror for packages that have dissapeared upstream.
https://jira.digi.com/browse/DEL-1493
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit 0a01d3a5d0203d1ce75482677739bf0113da624d)
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)
Yocto 1.7 Dizzy added support for os-release file in a new recipe, so
we need to remove it from our base-files bbappend in order to avoid
conflicts between both packages.
https://jira.digi.com/browse/DEL-1390
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This can be used as a template for size optimized images. It constraints
the use of X11 related packages and the image types used.
To build, add the following to your conf/local.conf:
DISTRO_FEATURES_remove = "x11"
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Javier Viguera
Urko Nalda
Hector Palacios
Alex Gonzalez
Jose Diaz de Grenu de Pedro
Isaac Hermida
Paul Osborne