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 bbappend was added to be able to native build the util-linux
package in our old buildserver (with Debian 6). This is no longer needed
as we migrated our buildserver to newer Debian.
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>
Added 'meta-python' to bblayers.conf.sample as it's now a dependence of
'networking-layer'. Otherwise if fails with:
ERROR: Layer 'networking-layer' depends on layer 'meta-python', but this
layer is not enabled in your configuration
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>
Some minor enhancements to mkproject script:
* Add 'conf-notes' files with DEY specific information. This is shown
when you create the project or when you reload the environment in an
already created project.
* Create a 'dey-setup-environment' script in the project's folder that
allows to reload the environment in a new terminal.
* Remove the PATH variable tweaking. This was needed in older versions
of Yocto, where the PATH kept growing each time you reloaded the
environment, but it has been fixed in poky, so there is no need to do
the same in our mkproject script.
https://jira.digi.com/browse/DEL-1150
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>
Add possibility for other layers to add additional features for UBIFS creation,
e.g. "-R <rp_size>" for super-user reserved pool.
Signed-off-by: Robert Hodaszi <robert.hodaszi@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>
These are key packages that we may need to debug in the buildserver, so
do not remove the object files.
Signed-off-by: Javier Viguera <javier.viguera@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>
Javier Viguera
Alex Gonzalez
Robert Hodaszi