This daemon (rngd) feeds random data from hardware device to kernel
entropy pool.
https://jira.digi.com/browse/DEL-2501
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
As of Yocto 2.0, the cryptodev module used as interface between
user-space and hardware encryption is the version 1.7.
According to that cryptodev's version documentation, the cryptodev
engine in openssh is outdated:
https://github.com/cryptodev-linux/cryptodev-linux/blob/cryptodev-linux-1.7/README
They provide an URL with two patches to update openssl. This commit
forward port those patches to the Openssl version used in this version
of Yocto.
https://jira.digi.com/browse/DEL-2501
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
COMPATIBLE_MACHINE is a regular expression, so we need to update the current
pattern for ccimx6 due to it will also match with ccimx6ul.
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
That restriction does not make any difference in the final image
contents, because no package depending on X11 is added to the image, and
it prevents the image from being built with the default DEY
configuration (that has X11 distro feature enabled).
This also allows to build the image in the buildserver with the same job
that builds other X11 based images.
https://jira.digi.com/browse/DEL-2106
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Use LAYERDEPENDS to configure the layer dependences for meta-digi-arm
and meta-digi-dey.
https://jira.digi.com/browse/DEL-1129
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Otherwise building the demo application fails with:
| DEBUG: Executing shell function do_configure
| Project ERROR: Unknown module(s) in QT: svg
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This patch adds a udev rule and a script to detect HDMI hotplug and create
the HDMI audio pulseaudio sink if needed (that is, if the system was
booted with no HDMI cable plugged).
https://jira.digi.com/browse/DEL-2327
Signed-off-by: Jose Diaz de Grenu de Pedro <Jose.DiazdeGrenudePedro@digi.com>
A patch sent upstream has been finally merged so this commit is not
needed anymore.
This reverts commit 6a66656161.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
module-udev-detect blocks the sound interface on boot for about five
seconds while detecting the hardware. This patch removes it so that
module-detect is used instead, which uses static hardware detection and is
faster.
https://jira.digi.com/browse/DEL-2218
Signed-off-by: Jose Diaz de Grenu de Pedro <Jose.DiazdeGrenudePedro@digi.com>
Move this variable to DEY distro conf so that it is available for any
recipe built with the distro.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-2192
There is another OpenGL demo application QT5 Hello Windows for testing
purposes.
https://jira.digi.com/browse/DEL-2184
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
It has been observed that the wireless interface ocassionally fails to resume
from suspend on extensive long run validation testing, so we workaround it by
bringing the interface down before suspend and bring it up again after resume
This reverts commit a77cd1406d.
https://jira.digi.com/browse/DEL-2217
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
This image provides a demo rootfs with QT. It can be built for
framebuffer and also for X11.
https://jira.digi.com/browse/DEL-2196
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
We were masking meta-fsl-arm linux recipes to clean some warnings on
bitbake parsing. This does not happen anymore with new versions of
Yocto, so just remove this BBMASK.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This install the 'obexd' server which is needed for the QT5 bluetooth
file transfer example applications.
https://jira.digi.com/browse/DEL-2147
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Generalize bluetooth support so it can be used not only with bluez4 but
with bluez5 as well. Use EXTRA_QMAKEVARS_PRE to pass the packageconfig
options to the do_configure task.
https://jira.digi.com/browse/DEL-2147
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This is a user-space workaround for the reboot/poweroff problems we
are having in the ccimx6sbc. Seems that they are not reproducible when
only one core is enabled, so the workaround is to disable the rest of
the cores for rebooting/halting.
https://jira.digi.com/browse/DEL-2133https://jira.digi.com/browse/DEL-2148
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit a9e36a74bb20ab38f220116ba2742dca3d80c293)
Also initialize the video sink to 'glimagesink' in case it has not been
configured from the environment, but only for the X11 application
(gtk-play). This recipe also provides a command line application for
framebuffer (gst-play) that is not affected by this change.
https://jira.digi.com/browse/DEL-2132
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
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>
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>
Also remove config entries in '/etc/network/interfaces' if corresponding
variable is not defined.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Allows to configure static DNS servers in resolv.conf setting following
variables in your project's config file:
ETH0_STATIC_DNS, ETH1_STATIC_DNS, WLAN0_STATIC_DNS
Those variables accept multiple dns servers (separated by spaces)
https://jira.digi.com/browse/DEL-1266
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Use the package manager postinst framework to run the rootfs resize
script on first boot after the image has been flashed to the EMMC.
https://jira.digi.com/browse/DEL-1317
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
microwindows makefiles override some environment variables set by
bitbake. This makes the build fail with:
fatal error: gnu/stubs-soft.h: No such file or directory
Force those variables by passing them via the make command line.
https://jira.digi.com/browse/DEL-1319
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
* CONFIG_FEATURE_IFUPDOWN_EXTERNAL_DHCP to support 'connmand' for dhcp.
* CONFIG_CTTYHACK to make easier boot from an initramdisk.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
No longer needed because a patch with the same functionality was
accepted upstream (meta-fsl-arm).
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This was added in the past (dey-1.4) as a workaround for reboot/poweroff
issues not completing properly [DEL-633]. At that time the util-linux
umount command worked while the one from busybox didn't. Now this
workaround is not needed anymore. The reboot/poweroff commands complete
correctly with busybox' umount, so just remove the runtime dependence.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This is now needed in yocto 1.7. Otherwise it fails with:
ERROR: Please ensure recipe packagegroup-dey-gstreamer.bb sets PACKAGE_ARCH before inherit packagegroup
ERROR: Please ensure recipe packagegroup-dey-examples.bb sets PACKAGE_ARCH before inherit packagegroup
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This installs 'libbluetooth.a' in the toolchain (needed to build static
binaries that use libbluetooth).
https://jira.digi.com/browse/DEL-1303
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit f53ae4ab2af1bc5dd2f3f38f9d351d9eefd1f163)
Start the application with a well known rotation value that works with
all the resolutions. Otherwise the rotation value is unknown because it
could have been changed in a previous run of the application.
Also in the kernel driver support was added to report EINVAL to
user-space in case the requested rotation is not supported. We use that
to not return from the 'v4l2_rotate' function without enabling again
the overlay preview.
https://jira.digi.com/browse/DEL-1068https://jira.digi.com/browse/DEL-1205
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit 2f7547a1b810683b813b708ba67e53ba156a9337)
The camera/driver does not support a cropping rectangle with height and
width less than 8 pixels. Add those limits to the sanity check of the
values in the user-space test application.
https://jira.digi.com/browse/DEL-1201
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This allows to easily build QT applications sourcing the toolchain
environment setup script and then running:
$ qmake -project
$ qmake
$ make
https://jira.digi.com/browse/DEL-1003
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The adt-installer hardcodes the distro version in URL paths to
yoctoproject website. This is ok if you control the website and the
versioning of the distro (for example using Poky as distro).
In DEY the versioning is not compatible with the content of the website,
so just blacklist the recipe. If anyone needs the adt-installer they can
download it from the Yoctoproject.
https://jira.digi.com/browse/DEL-1003
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Add the 'mkimage' host tool to the toolchains generated with 'bitbake
meta-toolchain' or with 'bitbake -c populate_sdk <image>'.
This allows to use the standalone toolchain to build kernel images of
type uImage (with u-boot header)
https://jira.digi.com/browse/DEL-1003
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
We used to have these poky references to make 'adt-installer' happy when
built using DISTRO=dey.
But this has side effects on the standalone toolchain created with
'populate_sdk'. The standalone toolchain installer has:
* default install path referring to poky instead of dey
* default toolchain version not matching our DEY version
This is misleading for customers, so rework the distro config file
prioritizing the standalone toolchain over the adt-installer.
https://jira.digi.com/browse/DEL-1003
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
We used to have two distros:
DEY: without X11 support
DEY-GUI: with X11 support
After the change, we have just one DEY distro with X11 support. At the
same time add a CONFLICT_DISTRO_FEATURE to dey-image-minimal so it
cannot be built with X11 distro feature enabled. So now in order to
build 'dey-image-minimal':
DISTRO_FEATURES_remove = "x11"
needs to be added to your project's local.conf file.
https://jira.digi.com/browse/DEL-858
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
NETWORK_MANAGER is a packagegroup-core-x11-sato recipe variable, so
override it in a bbappend instead of at a distro level.
At the same time remove a useless WEB variable from the image recipe.
WEB is a packagegroup-core-x11-sato local variable as well, and
overriding it in another recipe does not have any effect, so just
remove it.
https://jira.digi.com/browse/DEL-858
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This was working in dey-1.4 because there was a basic support for static
nodes in poky. They removed it in Yocto 1.6.
We still need this functionality, so add it here in the bbappend.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
gobject introspection is not supported in Yocto, so there is not a
python binding package to use it.
Bluez4 uses such functionality in some of the test scripts. This patch
replaces it with the legacy pygobject, so they can work again.
https://jira.digi.com/browse/DEL-1274
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
* Remove inconditional inclusion of dey-gstreamer: dey-image-minimal
includes dey-gstreamer if MACHINE_FEATURES contains 'accel-video'
so dey-image-graphical inherits this from dey-image-minimal.
This does not make any difference for IMX platforms but allows to
remove inconditional inclusion of dey-gstreamer for MXS. To allow
'gaku' (sato audio player) playing MP3 files COMMERCIAL_AUDIO_PLUGINS
is added to the distro config file.
* Only include 'owl-video' if MACHINE_FEATURES contains 'accel-video'.
* Remove inconditional inclusion of qt4-examples from dey-qt
packagegroup. Package qt4-examples is part of the RRECOMMENDS for
package qt4-demos, so it will be included anyway and not having it
hard-coded allows to bad-recommend it for some platforms and not
for others.
* Use BAD_RECOMMENDATIONS to avoid inclusion of 'qt4-demos-doc' package
for all platforms (this package does not add any value and weights
about 50MB) and 'qt4-examples' for ccardimx28js.
With all those changes, we get a graphical image with GTK + QT that fits
in the standard rootfs partition for ccardimx28js.
https://jira.digi.com/browse/DEL-1164
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This package was used in 'meta-fsl-demos' layer, but was deprecated and
removed. It includes desktop launchers for QT4 demo/example apps. We
still show those demo apps, so integrate the launchers directly into a
qt4 bbappend.
https://jira.digi.com/browse/DEL-1164
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The interfaces file is now dynamically created for eth0, eth1 and wlan0. By
default they are configured if enabled in the machine features, and have
the same static configuration as before.
The static IPs can be configured as follows:
ETHn_STATIC_IP = "<ip address>"
ETHn_STATIC_NETMASK = "<netmask>"
ETHn_STATIC_GATEWAY = "<gateway>"
WLAN0_STATIC_IP = "<ip address>"
WLAN0_STATIC_NETMASK = "<netmask>"
To configure dynamic IPs you can use the following configuration in your
local.conf:
ETHn_DHCP = "dhcp"
WLAN0_DHCP = "dhcp"
https://jira.digi.com/browse/DEL-1178
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
By removing the driver on ifdown and loading it on ifup we workaround some
problems found in long run suspend stability testing.
https://jira.digi.com/browse/DEL-1084
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This removes the Openembedded logo and leaves the kernel splash until
the desktop is ready.
https://jira.digi.com/browse/DEL-1131
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Override the default from meta-fsl-arm for MX6 which is configured for
eGalax touchscreen.
We create an empty calibration file because the Fusion touch works just
fine without calibration.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This was needed to overcome some corner cases with storage devices on
suspend/resume using MDEV as device handler.
Now we are using UDEV and after some tests done it seems that the
'resume_storage_devices' hack is not needed anymore.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
udhcpc's '-R' option means 'Release IP on exit'.
This fixes a strange corner case on reboot: if you configure your network
interface to DHCP in '/etc/network/interfaces' AND you have some NFS
share mounted on your system, then running reboot command fails to
complete and it hangs on:
'Unmounting local filesystem'
This happens because on reboot TERM and KILL signals are sent to all
the processes in the system before umounting the local filesystem. When
udhcpc daemon receives the signal it exits and releases the IP (because
it was launched with '-R') leaving an unconfigured network interface
that later is unable to umount a network filesystem (NFS), resulting on
'reboot' command being unable to complete.
Removing the '-R' option from udchpc allows to kill the process without
unconfiguring the network interface.
https://jira.digi.com/browse/DEL-1125
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The original defconfig came from DEL. Make the defconfig more similar to
the Yocto default one.
This restores the default udhcpc options when running via ifup to '-R
-n'. This is important because without '-n' the target can wait forever
to get an IP on boot while maybe the network is not available.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
In Yocto Daisy mplayer is not supported. Trying to build it fails with:
ERROR: Nothing PROVIDES 'mplayer'
ERROR: mplayer2 PROVIDES mplayer but was skipped: Recipe is blacklisted: Requires newer libav which has negative D_P
This is because it has been blacklisted in commit:
http://cgit.openembedded.org/meta-openembedded/commit/?id=2e7f3ce93b2c9864037fba8cc68fde46aafac4b0
The reason is that is has a build-time dependence on libav being newer
than the one provided by Yocto.
We don't use mplayer on ccimx6 as it has accelerated video using
gstreamer, so just remove the bbappend for this release.
Probably we need to revisit this when we upgrade our ccardimx28 support
to new versions of Yocto and upstream has removed the recipe from the
blacklist.
https://jira.digi.com/browse/DEL-1075
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Those hacks were added to fix a problem when building development images
(with 'dev-pkgs' image feature enabled). In that case the developemnt
packages (libdigi-dev and microwindows-dev) have a dependence on the
normal packages (libdigi and microwindows). But those packages are not
created by default because they are empty, thus the needed ALLOW_EMPTY hack.
Fix the problem by just resetting the runtime dependences of the -dev
packages. This allows to not create empty libdigi and microwindows
packages.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>