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>
The bbappend was created mostly to install an old version of the
'simple-agent' test application (the one included in the package was
failing) but upstream (Poky) has fixed most of the issues, so our
bbappend is just needed now to enable 'health' profile support.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The 1.5+snapshot.new tag does not work, so until there is an official 1.6
release use the last 1.5.1 SDK.
Fixes https://jira.digi.com/browse/DEL-988
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This packages was removed from 'meta-fsl-demos' and it's needed in our
graphical image, so for the moment add it to meta-digi-dey layer.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Javier Viguera
Alex Gonzalez