We originally ignored the weston-init.bbappend in meta-freescale back in thud
because we were basing our recipe off of NXP's sumo BSP, and NXP's weston-init
customizations were incompatible with the ones in meta-freescale. Remove it
from the BBMASK to be able to incorporate the customizations in meta-freescale.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Rework the weston-init recipe and add a BBMASK to ignore meta-freescale's
weston-init.bbappend file.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Update the README as well to reflect this change, since the ftp protocol might
be blocked in some corporate networks.
https://jira.digi.com/browse/DEL-6880
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Since the final image name is not available in a global scope, append it to the
default installation path in the SDK extraction script once it has been
packaged.
The new default installation path format is:
/opt/dey/<version>/<platform>/<image>
https://jira.digi.com/browse/DEL-5264
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
After some fixes to cloudconnector, all packages compile with the standard
GCC version in Yocto Thud (gcc 8.2).
Some other packages are broken if we do not use the expected GCC version for
Thud. Specifically, this was detected trying to compile docker.
This reverts commit ddd14144c3.
There's a recipe in the thud branch of meta-openembedded specifically for the
opencl-headers package, but it's also provided by imx-gpu-viv. This generates
build errors when parsing the recipes and when populating the sysroot for
opencv.
https://jira.digi.com/browse/DEL-6603
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Make our vulkan sub-folder match NXP's by updating recipes, deleting ones that
are no longer needed and adding new ones. Also, stop forcing 1.0.65% as the
preferred vulkan version.
https://jira.digi.com/browse/DEL-6603
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Update u-boot-fw-utils patches to apply on current upstream version. Remove
recipe for version 2017.09 since both U-Boot v2017.03 and v2018.03 work fine
with the newer version.
https://jira.digi.com/browse/DUB-881
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
This version is only required to build U-Boot 2017.X, so select it as preferred
version only on those platforms that build this U-Boot (CC6 and CC6UL).
https://jira.digi.com/browse/DUB-881
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
In 92c49b9b1a16dfd35444db8143bd4cae4cda70cc was introduced the LAYERSERIES_CORENAMES
and LAYERSERIES_COMPAT_<layername> with the intention of allowing layers
to indicate which versions of the core project they're compatible with.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Also add gtk3+ and clutter demos that depend on wayland since they are also
included in NXP's images.
https://jira.digi.com/browse/DEL-6104
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The MACHINE_EXTRA_RRECOMMENDS for the ccimx6ul in meta-digi-arm contains
cryptoauthlib. If we want to use meta-digi-arm as a standalone BSP layer
we need to move the cryptoauthlib recipe to meta-digi-arm, that or not make it
a machine dependency.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This is the stack covered by the Bluetooth certification. We will keep
it even though the newer bluez 5.46 will be used by default.
https://jira.digi.com/browse/DEL-5518
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
Pending to update the patch for dynamic environment location in NAND.
https://jira.digi.com/browse/DEL-5518
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
Tweaked to maintain some recipes' revisions to AUTOREV instead of the
fixed SHA1s from the tag.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The removed distro features are mostly corner cases, not widely used,
and sometimes conflict with other packages serving the same purposes.
For example:
* '3g' only adds ofono for cellular support, while we are
using ModemManager.
* 'nfc' adds 'neard' the NFC daemon (which at the moment we don't
support)
* 'zeroconf' adds 'avahi' package, but we are using NetworkManager
instead to manage the network interfaces.
* 'nfs' adds 'rpcbind' server, which is not needed at all to have
an NFS mounted rootfs.
Needless to say that all those packages can be added to any image
without having the distro features enabled, or if preferred, you can add
the distro features back in the project's local.conf.
https://jira.digi.com/browse/DEL-3780
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
- In Jethro, swupdate recipe was using 'swupdate_git.bb' as the main recipe to
build. In morty that recipe has been disabled and the '2017.01' one is used
instead, so we have to append to this new recipe by renaming our existing one.
- Our bbappend will now point to the same SHA1 that is being used, so we can
remove the SRCREV.
- The new code already includes the progress client patch, so it has been removed.
Signed-off-by: David Escalona <david.escalona@digi.com>
- Added the new image type 'recovery.vfat' to the DEY images
generation process. This new image is a clone of the 'boot.vfat'
but including the recovery ramdisk and the recovery boot script.
- Added the new image type 'recovery.ubifs' to the DEY images
generation process. This new image is similar to the 'boot.ubifs'
but including the recovery ramdisk and the recovery boot script.
Signed-off-by: David Escalona <david.escalona@digi.com>
Gabriel Valcazar
Mike Engel
Arturo Buzarra
Jose Diaz de Grenu
Gonzalo Ruiz
Alex Gonzalez
Javier Viguera
David Escalona