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>
Jose Diaz de Grenu de Pedro
Isaac Hermida
Javier Viguera
Alex Gonzalez
Paul Osborne
Hector Palacios