Update a patch so it applies cleanly and remove another one, since it has
already been applied upstream
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This package was originally being added via RDEPENDS, and its removal was
missing when porting the newer file from NXP's meta-imx. Re-incorporate the
removal to avoid including the package in our images, but do so by adding it
to our images' BAD_RECOMMENDATIONS.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Even though our busybox recipe (v1.34.1) is backported from poky's honister
branch, it has many elements in common with the recipe provided from poky's
hardknott branch (v1.33.1). To simplify our backport, re-use poky's busybox
files when possible, replacing them only when strictly necessary.
While at it, remove the busybox-inittab recipe, since there are barely any
differences between the honister and hardknott versions.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This PACKAGECONFIG existed in gatesgarth, but it's included by default in
hardknott and it pulls in libgbm as a dependency. This package isn't available
for i.MX6 platforms, causing the build to fail immediately. Remove this from
the ccimx6 PACKAGECONFIG and leave it how it was on gatesgarth.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
For packages such as weston or opencv, bitbake will sometimes choose the poky
recipes, causing build errors. Explicitly set the NXP version of these packages
as the preferred version by mimicking the layer.conf configuration in the
meta-bsp layer of meta-imx.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
We now use the meta-freescale recipe as a base for our .bbappend, so remove
the filter.
This reverts commit 9e68d61f7c465800d62913c044e43c541f2eacd7.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Aside from the file paths changing, there are a few cosmetic differences
between v1.22.14 and v1.30.4 that prevented the patches from applying, so
re-work them.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The common license file GPL-2.0 is now called GPL-2.0-only in poky, so we need
to reflect this name change to avoid errors
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is a generic package that is currently being used by NXP to load firmware
on the target, so include it in our images as well. Since it only works with
systemd, leave it out of builds that use sysvinit.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
poky now provides glibc v2.33 by default, and there aren't any alternative
versions available, so there's no need for this.
This reverts commit e7921dfd93.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Remove the v3.0.8 version of the recipe to use the v3.0.9 recipe in poky. Also,
adapt our .bbappend since some of its changes are outdated.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Most of the changes are cosmetic (copyright years and whitespace). Update
gstreamer1.0-plugins-good-qt to v1.18.5, remove outdated patch for said package
and sync qtwayland recipe.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
We initially backported v4.5.2.imx into gatesgarth, but since that version is
already available in meta-freescale, remove the base recipe and keep only the
.bbappend.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Add custom NXP daemon.conf, new NXP patch and adapt ccimx6ulsbc patch to apply
cleanly over v14.2
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Sync the .bbappend while keeping our ccimx6 patch and remove the 9.0.0.imx
recipe, since it's already available in meta-freescale.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Remove recipes that are available in the community layers, include a new
.bbappend for python3-matplotlib and update the .bbappend for python3-wheel
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This patch was initially needed for a specific version combination of
NetworkManager (>= v1.22) and glib-2.0 (v2.63.3 - v2.64.X), but since the
hardknott branch of poky now provides glib-2.0 v2.66.7, the patch isn't
needed anymore.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
We initially added newer versions of the recipes related to WPE Webkit in order
to incorporate performance improvements, but the hardknott branch of
meta-webkit includes even newer versions, so we can remove our recipes.
Reflect this change in our distro config file.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The weston recipe we ported from NXP's meta-imx layer has the same name,
causing warnings to appear when applying our patches. To avoid confusion,
ignore the meta-freescale version of the recipe so that ours is the only
option.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
(cherry picked from commit 9e68d61f7c465800d62913c044e43c541f2eacd7)
Otherwise, the .bbappend applies to all existing weston recipes, and since our
patch is only available in our layer, bitbake will print warnings about the
patch not being found for those other recipes. This is harmless, since DEY
always uses NXP's version of weston, but it can be confusing, so avoid the
warnings altogether.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
(cherry picked from commit d4464a8211bff6b315a8ed5d094b8c25099f4130)
Digi Embedded Yocto 3.2-r2.2
Manually changed recipes to use the master branches instead of the fixed SHA1
from the last release.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
SQUASHFS read-only rootfs cannot be unencrypted on-the-fly
so skip encryption if read-only-rootfs is active.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
When TrustFence and a read-only rootfs are enabled, U-Boot must
authenticate the SQUASHFS root file system. Add config switch to force
U-Boot to authenticate this image.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
This mode is necessary in the recovery initramfs to be able to properly detect
any external storage device that might contain an update package. The
configuration option associated with this mode became explicit after upgrading
busybox to v1.34.1, so enable it in our defconfig.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The nand devices doesn't need to call the mount_cryptrootfs
script.
Reported-by: Francisco Gil <francisco.gilmartinez@digi.com>
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Some recipes were forcibly removing conflicting packages.
This does not allow to add those packages back for users that
want to use meta-digi layer, but a different distro than 'dey'.
With the 'dey' distro override, such removals are only done
if using this distro.
Reported-by: Michael Burr <michael.burr@digi.com>
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://onedigi.atlassian.net/browse/DEL-7712
In the cc6ul we are not powering-off the supply of the XBee.
This is making that after a suspend/resume action the XBee
hangs due to ModemManager hasn't been stopped before the suspend.
Stopping ModemManager before going to suspend solves the issue.
https://onedigi.atlassian.net/browse/DEL-7701
Signed-off-by: Francisco Gil <francisco.gilmartinez@digi.com>
Since commit 11558352 ("swu-images: add "installed-directly" flag to
sw-description") the swu package images are streamed into the target without
any temporary copy to support devices with low memory available, that forces a
different order according with the swupdate documentation because scripts
should packed before the rest. This means that all the pre, post and shell
scripts will be executed after the images will be installed. This behavior
breaks the current support to mount the cryptorootfs node before install an
encrypted rootfs.
This commit moves the shell script to mount the cryptorootfs node to the
recovery initramfs and modifies the swupdate command line to call the shell
script before the images installation.
https://onedigi.atlassian.net/browse/CC8X-320
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Since we added support for compressing rootfs images, we need to manage SWU
packages with a regular rootfs image and with compressed images. That support
was missing in the identification process when the SWU packet was verified.
This commit fixes the identification of compressed rootfs images.
https://onedigi.atlassian.net/browse/CC8X-320
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This recipe had a post install script to do the following:
- create runlevel symlinks.
- comment the 'auto' lines of /etc/network/interfaces if running on
a non-Wi-Fi variant.
- add Atheros or QCA bridge examples depending on the detected chip.
- add wlan1 interface only if QCA chip is detected.
This post install cannot run on a read-only-rootfs so the recipe has been
reworked to do the same things at build time:
- the runlevel symlinks have been removed because they are taken care
of by a poky class.
- add a pre-up condition (the existance of a wireless entry on the device
tree) so that the interface is not brought up if the condition is not met.
- for the cc6/cc6n, since the Wi-Fi chip can be Atheros or QCA, add
specific wlan1 and br0 fragments with a pre-up condition basing on the
detected ID of the Wi-Fi chip
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://onedigi.atlassian.net/browse/DEL-7708
The access point configuration files are dynamically modified on a post
install script to generate an SSID name based on the last digits of the
MAC address (physical or virtual) assigned to a wlanX interface.
On read-only file systems, this is not possible, so add some conditional
code to the do_install() to use instead the $DIGI_FAMILY name.
Caveat: if several identical SOMs with read-only-rootfs co-exist on the
same network as APs, they will identify with the same SSID.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://onedigi.atlassian.net/browse/DEL-7708
Some packages require different scripts, configuration files or installations
depending on the wireless chip assembled on the target. In general, the way
to support both chips in one image is to have the recipes install both
versions of the aforementioned files, then leave only the strictly necessary
version once the wireless chip can be deduced.
In the case of the init-ifupdown recipe, this involves installing temporary
configuration fragments that are later erased. In the case of the standby
script, the logic can be implemented in a single file.
https://onedigi.atlassian.net/browse/DEL-7661https://onedigi.atlassian.net/browse/DEL-7666
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This allows the packages to be included in the ccimx6sbc images. While at it,
include the Qualcomm bluez patches in ccimx6 builds. These patches aren't
destructive, they simply add functionality required by the Qualcomm chip, so
they shouldn't have any secondary effects when using the Atheros chip.
https://onedigi.atlassian.net/browse/DEL-7661https://onedigi.atlassian.net/browse/DEL-7666
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The latest version of psplash changed the default path to store the
communication FIFO with other processes to "/run" to allow keeping the
information between reboots, however we are using this tool from an initramfs
where "/run" does not exist, producing multiple errors trying to write to a
nonexistent path, delaying the update process.
This commit forces psplash to use an existing path like "/tmp" to handle the
communication FIFO, because we don't need to maintain the update information.
https://onedigi.atlassian.net/browse/CC8X-318
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The latest version of psplash changed the default path to store the
communication FIFO with other processes to "/run" to allow keeping the
information between reboots, however we are using this tool from an initramfs
where "/run" does not exist, producing multiple errors trying to write to a
nonexistent path, delaying the update process.
This commit forces psplash to use an existing path like "/tmp" to handle the
communication FIFO, because we don't need to maintain the update information.
https://onedigi.atlassian.net/browse/CC8X-318
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
These options should only be enabled when using SELinux, so apply them only
when "selinux" is in the DISTRO_FEATURES. The fragment is a copy of the one in
meta-selinux with the addition of DEFAULT_SECURITY_DAC and LSM.
https://onedigi.atlassian.net/browse/DEL-7641
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The default policy provided by meta-selinux breaks a lot of the features in
DEY, so adapt it to make most features work. Note that this is simply an
example, end users should create their own policies for their own needs.
Make these changes toggleable so that users can use the reference policy
instead.
https://onedigi.atlassian.net/browse/DEL-7641
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This packagegroup includes all of the userspace packages needed to use SELinux.
For now, use the same variant of the packagegroup, which contains all available
packages.
Since the meta-selinux layer isn't available in all platforms, implement this
change via a dynamic layer.
https://onedigi.atlassian.net/browse/DEL-7641
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This fixes the following CVEs:
* CVE-2021-3711
* CVE-2021-3712
Port the recipe and patches from the dunfell poky branch, since the hardknott
version contains additional changes aside from the revision update.
https://onedigi.atlassian.net/browse/DEL-7647
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This fixes the following CVEs:
* CVE-2021-3711
* CVE-2021-3712
Port the recipe and patches from the dunfell poky branch, since the hardknott
version contains additional changes aside from the revision update.
https://onedigi.atlassian.net/browse/DEL-7647
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Adapt the format_ubi_volume() function to wipe out UBI volumes
instead of formatting MTD partitions.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://onedigi.atlassian.net/browse/DEL-7614
The function uboot_getenv() is a wrapper over libuboot_get_env() and
requires that the returned strings are freed when no longer in use.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://onedigi.atlassian.net/browse/DEL-7645
(cherry picked from commit 27ce7a4f20)
- The function is only used internally in this file, so make it static.
- Convert the function from 'int' to 'bool', since no other values are
evaluated.
- Only return true if the variable 'dualboot' is set to 'yes'. Before,
the function returned true if 'dualboot' was different than 'no'.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
(cherry picked from commit 9a519570ba)
The use of this function, which is a wrapper over libuboot_get_env(),
requires checking if the returned string is NULL.
Manipulations of such string without checking whether it's NULL may lead
to segfault errors.
This was seen during firmware update on a device that didn't have the
'dualboot' variable set.
Reported-by: Chandrababu Pigilam <chandrababu.pigilam@digi.com>
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://onedigi.atlassian.net/browse/DEL-7645
(cherry picked from commit 8a4484bbd6)
The function uboot_getenv() is a wrapper over libuboot_get_env() and
requires that the returned strings are freed when no longer in use.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://onedigi.atlassian.net/browse/DEL-7645
- The function is only used internally in this file, so make it static.
- Convert the function from 'int' to 'bool', since no other values are
evaluated.
- Only return true if the variable 'dualboot' is set to 'yes'. Before,
the function returned true if 'dualboot' was different than 'no'.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
The use of this function, which is a wrapper over libuboot_get_env(),
requires checking if the returned string is NULL.
Manipulations of such string without checking whether it's NULL may lead
to segfault errors.
This was seen during firmware update on a device that didn't have the
'dualboot' variable set.
Reported-by: Chandrababu Pigilam <chandrababu.pigilam@digi.com>
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://onedigi.atlassian.net/browse/DEL-7645
NetworkManager's main library went through a major overhaul in v1.22, changing
the way it interacts with glib among other things. When using a NetworkManager
version equal or newer than v1.22 along with a glib version between 2.63.3 and
2.65, a race condition can happen, randomly causing segmentation faults.
Since Yocto 3.2 uses NetworkManager 1.22.14 and glib 2.64.5, the race condition
is reproducible, but it can be fixed with the patch introduced in this commit.
The patch in question is commit e4a690f5dd959e74b2d6054826f61509892c8aa7 in the
glib git repo.
https://onedigi.atlassian.net/browse/DEL-7523
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
NetworkManager's main library went through a major overhaul in v1.22, changing
the way it interacts with glib among other things. When using a NetworkManager
version equal or newer than v1.22 along with a glib version between 2.63.3 and
2.65, a race condition can happen, randomly causing segmentation faults.
Since Yocto 3.2 uses NetworkManager 1.22.14 and glib 2.64.5, the race condition
is reproducible, but it can be fixed with the patch introduced in this commit.
The patch in question is commit e4a690f5dd959e74b2d6054826f61509892c8aa7 in the
glib git repo.
https://onedigi.atlassian.net/browse/DEL-7523
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This commit sets the GLIBC version to 2.32. The newest
eIQ packages require a newer glibc, but since said packages
are optional, make sure to use the gatesgarth glibc version
by default.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://onedigi.atlassian.net/browse/DEL-7625
This commit add a verification into the recovery library to avoid
that it is executed when in dualboot mode.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://onedigi.atlassian.net/browse/DEL-7580
(cherry picked from commit 30aa4a7444)
This commit add a verification into the recovery library to avoid
that it is executed when in dualboot mode.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://onedigi.atlassian.net/browse/DEL-7580
swupdate has the necessary logic to handle compressed images, so take advantage
of this to save space and reduce update package transfer times.
https://onedigi.atlassian.net/browse/DEL-7582
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Since these images are highly compressable, this greatly reduces the amount of
space taken up by build artifacts.
Modify the code used to generate the .sdcard and .installer.zip files so that
they contain the decompressed .ext4 image.
https://onedigi.atlassian.net/browse/DEL-7582
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This commit adds the required libraries and packages to exercise the Google
Coral devices with Digi Embedded Yocto.
https://onedigi.atlassian.net/browse/DEL-7547
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
'mdev -s' run on ramfs initialization is able to mount external media already
detected but fails to automatically mount any media detected afterwards.
Running it as a daemon first it will also be able to mount any media detected
after 'mdev -s' is run.
Use argument '-d' to first run mdev as daemon in background.
Move 2 seconds delay to after mdev has been initialized to give external
hardware all the time possible to be successfully detected and mounted.
https://onedigi.atlassian.net/browse/DEL-7285
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
Otherwise, Yocto will use the recipes in meta-webkit, which are slightly older.
https://onedigi.atlassian.net/browse/DEL-7578
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
By default, we only support the latest versions of the webkit packages anyway,
so use a wildcard so we don't have to update the recipes every time a new
version is available.
https://onedigi.atlassian.net/browse/DEL-7578
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Igalia has included performance improvements for i.MX platforms in the latest
versions of different packages related to webkit. Even though the recipes for
these versions are not yet available in meta-webkit, we can add our own to
meta-digi to take advantage of these improvements.
Update the cog patches so they apply cleanly over v0.9.90.
https://onedigi.atlassian.net/browse/DEL-7578
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This commit adds some swupdate parameter to select the sw-description
configuration depending on the used platform.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
Without this call, swupdate will be built with a default configuration which
is incompatible with our package format. Even though this function is already
called in the original recipe, it was done in the package's "git" directory.
Make sure the function is called at least once so that our defconfig is used in
the build.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Commit 28d9e025ea used += to append
a dependency to RDEPENDS but this was not working fine and was removing
previous dependencies.
Use instead _append override.
Reported-by: Francisco Gil Martinez <francisco.gilmartinez@digi.com>
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
Otherwise, swupdate will treat the update process like it's an OTA one and it
will try to store the package contents in /tmp, which won't fit.
swupdate commit 8b70ae5796e75c2ff856e8c46b3a3c09cb8fcccd states that all local
SWU packages should include this flag, since the old implementation had this
information implicitly.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Technically, partition unencryption is safe to do in open devices, although it
implies that at least one partition has already been encrypted. If we aren't
going to encrypt any partitions, there's no need to print the warning.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Instead of checking for the existence of /proc/mtd, which might lead to false
positives, check the "root" parameter in /proc/cmdline. Assume eMMC in case of
any error.
https://onedigi.atlassian.net/browse/DEL-7539
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
There are some init packages from the poky layer that remain using only a SysV
init script. Systemd converts these init scripts to systemd service format on
boot and shows an ugly warning for each one. To avoid flooding the console with
this kind of messages, we reduce the verbosity of these messages.
https://onedigi.atlassian.net/browse/DEL-7540
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
In the libubootenv implementation of fw_setenv, multiple variables can be set
in one call. When setting a variable with a space-separated list, the app
interprets the list as new variable/value tuples, for example:
fw_setenv myvar value1 value2 value3
Results in:
myvar=value1
value2=value3
This was causing the encrypted eMMC partition mechanism to break, because the
list of encrypted partitions is stored as a space-separated list in an
environment variable. Avoid this by enclosing the variable argument of
set_uboot_var() with double quotes.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Update version from 2.28.1 to 2.32.0, remove patch that is already included in
the source tarball and stop removing the qtwpe PACKAGECONFIG, since it's no
longer being included by default.
https://onedigi.atlassian.net/browse/DEL-7545
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Update the version from 0.7.1 to 0.8.0 and remove two patches that are already
being applied in meta-webkit.
https://onedigi.atlassian.net/browse/DEL-7545
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Before using the encrypted partition functionality, users have to manually
install the encryption key in the system. Failing to install said key will
result in errors later on.
Even though the installation isn't a difficult operation from a user's point of
view, the recovery script has the necessary logic to detect cases where a
partition is going to be encrypted with no key installed. Automatically
generate a key in these cases to avoid undesired behavior and to improve the
overall user experience.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This version adds new functionality to check if an encryption key is installed
as well as a fix for an issue that happens when encrypting partitions with long
names (over 12 characters).
https://onedigi.atlassian.net/browse/DEL-7535
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
If we trigger a key change while there are partitions that are encrypted,
print a warning and ask for confirmation so users know that the operation will
erase the contents of said partitions.
Like in the partition (un)encryption mechanism, add the possibility to skip
both the warning message and the confirmation prompt.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This initramfs only makes sense in platforms with an eMMC as the internal
storage, due to how the partition encryption support is implemented. In
plaatforms that use NAND instead, ths initramfs offers no functionality and
increases the recovery image size, so remove it.
https://onedigi.atlassian.net/browse/DEL-7534
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
If we allow users to manually change the encryption status of the rootfs
partition, we run the risk of wiping it without flashing a proper replacement
image. Because of this, rootfs encryption status should be determined
automatically using information from the update package.
Have the recovery script parse the update package's description to determine
whether to encrypt the rootfs or not.
https://onedigi.atlassian.net/browse/DEL-7174
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This partition isn't blacklisted, but it should only be (un)encrypted when
providing an update package. Make it so that manual encryption status changes
for this partition aren't possible from the recovery library.
https://onedigi.atlassian.net/browse/DEL-7174
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Since the recovery script checks the update package before installing it, use
the package's description to indicate if the package is meant to encrypt the
rootfs or not. Also, remove the pre-install script from the ccimx6ul packages,
since the logic in the script to remove the encryption flag from the rootfs is
now in the recovery script.
https://onedigi.atlassian.net/browse/DEL-7174
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Previously, TRUSTFENCE_INITRAMFS_IMAGE was the only variable used to configure
rootfs encryption. Now that any partition can be encrypted and the rootfs
encryption still needs to be handled differently, use two variables instead.
* TRUSTFENCE_ENCRYPT_PARTITIONS to control partition encryption in general
* TRUSTFENCE_ENCRYPT_ROOTFS to control rootfs encryption
As with most trustfence functionality, enable both by default. Leave
TRUSTFENCE_INITRAMFS_IMAGE as an internal variable only.
https://onedigi.atlassian.net/browse/DEL-7174
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Since the update partition might be involved during a software update, we need
to make sure that its contents are accesible and safe when using the partition
encryption feature at the same time.
Mount and unmount the partition correctly if it's encrypted and cancel any
operations that will result in the deletion of the update package.
https://onedigi.atlassian.net/browse/DEL-7174https://onedigi.atlassian.net/browse/DEL-7422
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Add a new function to the recovery library to be able to encrypt/unencrypt any
partition on the internal storage media. Since it's a destructive operation,
add a warning message and a confirmation prompt that can be skipped if needed.
Reflect this new functionality in the recovery-reboot app. Change the logic so
that an encryption key can be set even if there's no update package, because
now it's possible to encrypt other partitions while leaving the rootfs intact.
Also change the logic so that the app doesn't reboot into recovery mode if
there's no recovery command set.
Implement the same blacklist as the one in the recovery script.
https://onedigi.atlassian.net/browse/DEL-7174
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The partition encryption system now uses dynamically generated names for the
decrypted block devices, which are based on the partition name. Reflect this
change in places where the encrypted rootfs is referenced.
https://onedigi.atlassian.net/browse/DEL-7174
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Modify the recovery and trustfence initramfs scripts to be able to encrypt any
partition on the internal storage media, not just the rootfs.
To implement this functionality, add a new recovery command called
'encrypt_partitions'. When used, this command must contain a comma-separated
list of the partitions that are to be encrypted by the end of the recovery
process, including partitions that were already encrypted beforehand. Any
partition that isn't in the list will be unencrypted. If the command is absent,
no changes will be made, but it's possible to pass an empty command to
unencrypt all partitions.
Include a blacklist to avoid encrypting partitions that shouldn't be encrypted,
such as partitions that need to be accessed by the ROM code/U-Boot or
partitions that contain encryption keys.
While at it, remove unnecessary "get_kernel_version" function from the script.
https://onedigi.atlassian.net/browse/DEL-7174
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The matchbox-terminal provides a GTK+ terminal application on the sato desktop,
however it has a dependeency of the virtual terminal emulator GTK+ widget
library (vte) that recently introduced a dependency with the icu package that
increase the rootfs size in 20MB. Since this is a sample application, remove it
to save space on the rootfs.
https://jira.digi.com/browse/DEL-7524
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This package adds a dependency of python3-xml that includes the python3 core
package, increasing the size of rootfs by 8MB.
https://jira.digi.com/browse/DEL-7524
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
packagegroup-core-x11-sato has a dependency on the gst-examples package and
adds a RRECOMMENDS for several packages including many codecs, enconders, etc.
We remove this package for the cc6ul platform to save space in rootfs.
https://jira.digi.com/browse/DEL-7524
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Add just one qt demo by default and move all of them to platforms with gpu
support, as platforms like cc6ul have few space available.
https://jira.digi.com/browse/DEL-7524
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The prebuilt 'athtestcmd' binary allows you to test tx/rx of the
Wi-Fi MAC, when the driver is loaded in test mode.
This is required for certifying Wi-Fi in products, so add it by
default for the ccimx6sbc.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-7444
(cherry picked from commit acb402fdcfa54d8d5519580ff7fcfb76fbed3f49)
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
Now libgpiod is not added automatically and we need to add the
dependence manually.
For more info see commit 4339c28ff4aa0264c34f4f183349aea20a5ff127 in
meta-openembedded layer.
https://jira.digi.com/browse/DEL-7522
Signed-off-by: Francisco Gil Martinez <francisco.gilmartinez@digi.com>
In the free meta-scale layer, the same entry "use-g2d = 1" is uncommented for
mx6dl and mx6q, however our ccimx6 platform has both machines in its
definition, so the same entry is uncommented twice and throws an unexpected
error. This commit adds a append in the install process to uncomment this entry
for the ccimx6 platform.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
vulkan has a dependency of vulkan-headers package that is not available
for the mx8mm platforms.
https://jira.digi.com/browse/DEL-7508
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Recipe system-monitor has a dependency with systemd package, however it was
added unconditionally for all platforms. This commit adds a protection to
include this recipe only when systemd is present in the DISTRO_FEATURES
https://jira.digi.com/browse/DEL-7508
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Commit 98d76037("recipes-qt: qt5: Update recipes to new BSP release
imx_5.4.70_2.3.0") removes the definition of the PACKAGECONFIG_MX8_GPU
variable, but its use had to be removed. This commit completely removes the
undefined variable.
https://jira.digi.com/browse/DEL-7508
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Simplify the structure of the recipe folder, if one version is not supported
we must use the COMPATIBLE_MACHINE overwrite
https://jira.digi.com/browse/DEL-7508
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Commit f7a354d("Generate image headers from their PNG source, while still
including them in dist tarball") provides a default PNG files removing the image
generation in build time. This commit overwrites the default PNG with one
customized by Digi.
https://jira.digi.com/browse/DEL-7508
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Commit ae479d86d1("libical: add PACKAGECONFIG glib and enable it by default")
introduces a workaround to fix the build with glib support and enables it
by default, but this support is unstable and this workaround is not needed on
v3.0.8. Added original recipe without that workaround to avoid the build issue.
https://jira.digi.com/browse/DEL-7508
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The "dhcp" software package has become unmaintained and thus has been
functionally replaced by "dhcpcd" (client) and "kea" (server).
https://jira.digi.com/browse/DEL-7508
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Modify the recovery-utils code to reflect the change (change in C header and
linked libraries)
https://jira.digi.com/browse/DEL-7410
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Sync with BSP release rel_imx_5.10.9_1.0.0 and remove unnecesary files
after most of them were updated in meta-freescale layer.
https://jira.digi.com/browse/DEL-7508
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Sync with BSP release rel_imx_5.10.9_1.0.0 and remove unnecessary files
after most of them were updated in poky layer.
https://jira.digi.com/browse/DEL-7508
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The 'distro_features_check' class has had its functionality expanded, as
a result the class has now been renamed to 'features_check'
https://jira.digi.com/browse/DEL-7508
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Commit a04e0ed79 ("libsoc: use python3 for python bindings") moves python
support to use python3.
https://jira.digi.com/browse/DEL-7508
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
NetworkManager recipe split the command line util in a different package, so we
added it in our default images.
https://jira.digi.com/browse/DEL-7508
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Refresh custom patches and removed all Fast Roaming patch series due to it is
already integrated in this version.
https://jira.digi.com/browse/DEL-7508
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This commit adds the support for the cryptodev
engine into OpenSSL. So OpenSSL can use hardware
accelerated support through the CAAM driver.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-7439
The previous SHA1 has been completely removed from NXP's opencv repo, so the
recipe must point to a new revision. Update to the revision used in the
zeus-5.4.47-2.2.0 branch of meta-imx.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Include by default support to Simultaneous Authentication of Equals (SAE) and
the standard IEEE 802.11w to Protected Management Frames, both required to
support the standard WPA3.
https://jira.digi.com/browse/DEL-7301
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Remove outdated wayland patch and remove NXP workaround for mx8mq platforms in
the weston-init recipe. These changes don't affect our platforms, but it's to
make sure that we're in sync with the latest version of NXP's recipes.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Most 8M families have the same GLES3 support, with 8M Mini being the exception.
See NXP commit cbb1793f1 ("imx-gpu-viv: Simplify GLES3_HEADER_REMOVALS").
https://jira.digi.com/browse/DEL-7397
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Use the same common files for both ConnectCore 8M platforms
https://jira.digi.com/browse/DEL-7397
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Use the same common files for both ConnectCore 8M platforms
https://jira.digi.com/browse/DEL-7397
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Aside from code improvements, this version includes fixes for the following
vulnerabilities:
* CVE-2020-25681
* CVE-2020-25682
* CVE-2020-25683
* CVE-2020-25684
* CVE-2020-25685
* CVE-2020-25686
* CVE-2020-25687
While at it, remove files that were inherited from an older vulnerability fix.
These files consist of scripts, patches and configuration files that already
exist in the original meta-openembedded recipe directory.
Remake lua.patch, since the diff context has changed in v2.83.
https://jira.digi.com/browse/DEL-7389
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
These changes were originally applied to the ccimx6 to fix a trailing effect in
the desktop, but we've recently discovered an HDMI hotplug issue on the
ccimx6qp that is also solved when using the g2d backend. Apply the workarounds
to both platforms.
https://jira.digi.com/browse/DEL-7380
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
In order to revoke SRKs in platforms with AHAB we need to set a mask
during the signing/encryption process.
Create new TRUSTFENCE_SRK_REVOKE_MASK variable to export the
SRK_REVOKE_MASK variable required by the imx-boot signing script.
The revoke mask is not necessary for signing/encryption of other artifacts,
so set it by default to 0x0.
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
The landing page for the WebKit examples has gone through a visual overhaul to
improve the overall user experience, so adapt its recipe accordingly. Since the
page now contains resources that are relatively large (such as images and
extensive stylesheets), remove its elements from the recipe directory and
obtain them from Digi's FTP server instead.
https://jira.digi.com/browse/DEL-7365
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The Qt WPE plugin has an implicit dependency with libgbm, which is only
available on i.MX8 platforms. Also, it pulls in several Qt dependencies,
increasing the total rootfs image size by about 50MiB. Remove said plugin to
completely separate Qt and WebKit functionality.
https://jira.digi.com/browse/DEL-7339
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This recipe installs some videos that can be used to test the WebKit's hardware
acceleration during video decoding. Modify the landing page to be able to
access these videos.
https://jira.digi.com/browse/DEL-7314https://jira.digi.com/browse/DEL-7339
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This recipe installs the main page of the WebKit examples, from which all other
examples can be accessed. For now, only include the WebGL examples.
Since the landing page recipe needs to know which WebGL demos are being
installed and the webserver path where everything is installed, move some of
the variables used in the webglsamples recipe into an *.inc file to be able to
re-use said variables in different recipes.
Use the Digi embedded documentation CSS file for now, so the landing page looks
more on-brand.
https://jira.digi.com/browse/DEL-7314https://jira.digi.com/browse/DEL-7339
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
We're going to be using the busybox http server to house the WebKit examples,
so we need to get rid of any files that might interfere with it. Keep the files
for the ccimx6ul, since it doesn't support WebKit.
https://jira.digi.com/browse/DEL-7314https://jira.digi.com/browse/DEL-7339
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This recipe installs a subset of the samples available at
https://webglsamples.org/ onto the target's web server, to be able to run said
examples locally without needing internet access. Make sure not to install any
source files to avoid making the package too large.
https://jira.digi.com/browse/DEL-7314https://jira.digi.com/browse/DEL-7339
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Add two patches to improve user experience, such as making the browser
fullscreen and removing the otherwise necessary --platform parameter.
Also, make www.digi.com the default URI to avoid having to explicitly pass a
URI when launching cog.
https://jira.digi.com/browse/DEL-7311https://jira.digi.com/browse/DEL-7339
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The i.MX8X video decoder requires a specific NXP video converter, otherwise
videos will appear with several glitches. This patch adds said plugin in the
WPE webkit's internal gstreamer pipeline.
https://jira.digi.com/browse/DEL-7311https://jira.digi.com/browse/DEL-7339
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The EGL library provided by NXP in the v5.4.47 BSP has a bug where a NULL
pointer is returned by eglGetProcAddress() when trying to obtain the entrypoint
for a specific function used throughout the cog code. This caused cog to crash
immediately after launching it.
Recently, a fix was made available in the cog repo, so backport it to the
latest available revision of cog in meta-webkit and apply it.
https://jira.digi.com/browse/DEL-7311https://jira.digi.com/browse/DEL-7312https://jira.digi.com/browse/DEL-7339
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This image is very similar to dey-image-qt, but it includes the WebKit
packagegroup instead of the Qt one. Said packagegroup contains all of the
elements needed to run a WebKit-based browser environment in DEY.
This image requires the meta-webkit layer, so include it in our default
bblayers template. For now, include all WebKit related recipes in a dynamic
layer, because the ccimx6ul doesn't support WebKit and its projects don't need
meta-webkit at all.
https://jira.digi.com/browse/DEL-7339
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Create scripts to install DEY firmware using a USB stick.
https://jira.digi.com/browse/DEL-6802
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
configure power LED for blinking in standby
configure power LED solid on after resume
https://jira.digi.com/browse/DEL-7330
Signed-off-by: Hector Bujanda <Hector.Bujanda@digi.com>
Includes:
xserver-xorg: Upgrade to 1.20.8 version [YOCIMX-4697]
Backport the recipes from poky master as the xserver is already upgraded to 1.20.8.
Signed-off-by: Neena Busireddy <neenareddy.busireddy@nxp.com>
xserver-xorg: Remove comment that is no longer valid
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
xserver-xorg: Fix patch fuzz
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
Signed-off-by: Hector Bujanda <Hector.Bujanda@digi.com>
Added FILESEXTRAPATHS_prepend to reuse some recipes from poky layer.
Patches refreshed with devtool finish --force-patch-refresh
Signed-off-by: Hector Bujanda <Hector.Bujanda@digi.com>
Includes:
opencv: Add smaller version of download models script [YOCIMX-4899]
Add a download models script that downloads a subset of the
regular script, reducing the download size from 10 to 1 GB.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
opencv: Fix build break [YOCIMX-4806]
The fix for installing face_landmark_model.dat failed
if test was not in PACKAGECONFIG. In fact we should only
install face_landmark_model.dat if test is configured.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
opencv: Fix patch fuzz
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
Signed-off-by: Hector Bujanda <Hector.Bujanda@digi.com>
Includes:
imx-gpu-viv-6.inc: Update files in libopencl-imx package
Fix issue:
ERROR: imx-dpu-g2d-1.8.9-r0 do_package_qa: QA Issue: /usr/lib/libg2d-dpu.so
contained in package imx-dpu-g2d requires libOpenCL.so.1()(64bit), but no
providers found in RDEPENDS_imx-dpu-g2d? [file-rdeps]
Signed-off-by: Yuqing Zhu <carol.zhu@nxp.com>
imx-gpu-viv: Update library installation
The packaging model has been reworked so now we can simply
copy the libraries.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
imx-gpu-viv: Integrate recipe updates
Integrate our local recipe updates into the
copied include file.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
imx-gpu-viv: Copy include file from meta-freescale
Changes are extensive enough now that it makes sense to
simply copy what is upstream.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
kernel-module-imx-gpu-viv: Switch branch to imx_5.4.47_2.2.0
Signed-off-by: i.MX Yocto Project Build <imx.build@nxp.com>
imx-gpu-viv: remove wayland as a requirement for i.MX8 platforms
Based on commit ed2c4974 ("imx-gpu-viv: remove wayland as a requirement for
i.MX8 platforms"), this commit removes the requeriment of wayland as a backend
for the i.MX8 platforms to build framebuffer images.
https://jira.digi.com/browse/DEL-7013
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
imx-gpu-viv-v6: remove kernel-module-imx-gpu-viv dependency
This dependency was originally removed in commit
eafa8684a3, but it was erroneously put back in
commit 793e901678 when updating the recipe using
the one in meta-fsl-bsp-release as reference.
Instead of removing the line containing the dependency, in order to avoid the
same situation from happening in the future, comment it out and add an
explanation about why we're removing it.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Signed-off-by: Hector Bujanda <Hector.Bujanda@digi.com>
Includes:
Revert "weston-init: Fix being underrun with superTile format and video playing on i.mx8dxmek [YOCIMX-4227]"
The setting has been merged into driver [MGS-5713]
This reverts commit bfaf99da16df2b7fd56ec6454406d5a71e90aa9f.
Signed-off-by: Hector Bujanda <Hector.Bujanda@digi.com>
This commit replaces the hardcoded text from the readme file by the environment
variables adding from this way the release version to the file content.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Otherwise, qt5 applications will fail to launch on the 8X and 6/6QP.
https://jira.digi.com/browse/DEL-7281
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The indexes of the MCA PWM controllers are different in Linux v5.4, so the
default value used by libdigiapix results in an error. Reflect this change and,
while at it, replace the default PWM with an IO connected to a user LED to make
the example more visual.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Commit c24d1d96 ("sysinfo: adapt script after removal of deprecated fsl_otp
driver") introduced a mistake masking the SEC_CONFIG[1] bit read from the OTP.
This commit fix the read command to force it in hex format and finally match
with the mask in the script.
https://jira.digi.com/browse/DEL-7263
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Back when the ccimx6/6qp used Linux v4.9, we needed to use crda because
wireless-regdb-static wasn't supported until v4.15. Now that we use v5.4 on all
platforms, this workaround isn't needed anymore.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Commit c24d1d96 ("sysinfo: adapt script after removal of deprecated fsl_otp
driver") introduced support to determine if a device is closed by checking
a new boolean property on the DT for the CC8X platforms, however the CC8M
platforms use the same mechanism. This commit modifies the sysinfo script to
check also the DT for the CC8M platforms.
https://jira.digi.com/browse/DEL-7263
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Commit cbb38440 ("meta-digi-dey: sysinfo: Add chip revision sysinfo output")
introduced a new script variable to determine the SOC revision of the module.
However this entry only is available on the CC8X platforms. This commit checks
if the entry exist and then tries to read it to avoid unexpected issues with
devices without this entry.
https://jira.digi.com/browse/DEL-7263
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This version includes changes needed to reflect the OTP driver update in the
kernel.
https://jira.digi.com/browse/DEL-7261
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This commit adds new environment variables to support QT with wayland and
to fix the following error message when executing QT5 applications on the
target.
qt.qpa.plugin: Could not find the Qt platform plugin "eglfs" in ""
This application failed to start because no Qt platform plugin could be initialized.
Reinstalling the application may fix this problem.
Available platform plugins are: minimal, offscreen, vnc, wayland-egl, wayland, xcb.
Aborted.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
This commit updates the GPIO udev rules to change the group owner
and permission of the new gpio char driver. This will allow users
that belong to the digiapix group to access the char driver.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-7255
This package was being included as a RRECOMMENDS from libcrypto, but we don't
need it in the initramfs at all. Since our recovery image is already pretty big
compared with the recovery partition size on ccimx6ul platforms with 256 MB of
storage, remove it to make sure the image can fit.
https://jira.digi.com/browse/DEL-7253
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Add systemd auto-getty.service to run agetty on the console defined in the
kernel command line on platforms with systemd support.
This service replaces serial-getty@.service as the one responsible for
opening a tty port and prompting for a login name when
TRUSTFENCE_CONSOLE_DISABLE is configured.
https://jira.digi.com/browse/DEL-7242
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
We have specific scripts per platform to export the qt5 environment variables,
because using the default backend-specific scripts ported from the meta-imx
layer results in mismatches in specific cases (for example, 6UL framebuffer
images only support linuxfb, but the qt5-fb.sh script exports eglfs instead).
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
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>
The ccimx6 uses the g2d weston renderer to avoid graphical glitches, but the
default renderer code doesn't handle suspend/resume cycles properly, causing
other issues (notably in the framerate and the desktop not showing 66% of the
time when resuming from suspend). Add a patch to mitigate these issues.
https://jira.digi.com/browse/DEL-7236
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Without this option, moving any element on the desktop (cursor or windows) will
cause an undesired "trailing" effect, where parts of the moved elements remain
on the desktop.
https://jira.digi.com/browse/DEL-7221
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This workaround is no longer needed since ccimx6/6qp now use Linux v5.4
https://jira.digi.com/browse/DEL-7221
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Recipe from poky layer only provides the native support
but to generate the sdk we need also the nativesdk.
https://jira.digi.com/browse/DEL-7200
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This package needs to be installed in the rootfs for the demos to work.
While at it, mark this change as Digi-specific to avoid removing it in future
recipe updates.
Reported-by: Alfonso Martin Rey <alfonso.martinrey@digi.com>
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
(cherry picked from commit 07f1fa88f2)
This commit removes the v4l2 example because they are superseded
by gstreamer examples.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-7211
The old fsl_otp driver is deprecated and we need to determine
if the device is closed using a new property of the device tree
called 'digi,tf-closed'.
Assume the device is open if the property is not found.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-7185
(cherry picked from commit fc1a736758)
- OTP section
- Use just one fixed path to the OTP nvmem device descriptor (instead
of a loop).
- Use '-v' for dumping all values with hexdump.
- TrustFence section
- For cc8x, determine if the device is closed by checking a new boolean
property on the DT: digi,tf-open|closed
- For the rest, check the SEC_CONFIG[1] bit using the new nvmem
descriptor.
- Change log from 'Device status' to 'Security status'
- Report UNKNOWN if nvmem device does not exist.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-7185
(cherry picked from commit f6a8de0067)
The old fsl_otp driver is deprecated and we need to determine
if the device is closed using a new property of the device tree
called 'digi,tf-closed'.
Assume the device is open if the property is not found.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-7185
- OTP section
- Use just one fixed path to the OTP nvmem device descriptor (instead
of a loop).
- Use '-v' for dumping all values with hexdump.
- TrustFence section
- For cc8x, determine if the device is closed by checking a new boolean
property on the DT: digi,tf-open|closed
- For the rest, check the SEC_CONFIG[1] bit using the new nvmem
descriptor.
- Change log from 'Device status' to 'Security status'
- Report UNKNOWN if nvmem device does not exist.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-7185
By default, we generate SWU files which update both the linux and rootfs
partitions. This, along with the fact that platforms using NAND as the storage
media require a reboot for the rootfs partition's "enc" flag to take effect,
makes it safe to format the NAND's rootfs partition before performing an
update, regardless of having to encrypt the rootfs or not.
However, customers that wish to use the swupdate feature to update just the
linux partition will find that the rootfs is completely erased after the update
is finished, because a new rootfs hasn't been written in its place.
To avoid this scenario, parse the SWU package's description to verify that it
contains a rootfs image before formatting the partition.
https://jira.digi.com/browse/DEL-7067
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Upgrade GST version from 1.16.0 to 1.16.1
The headerfix.patch in gst-plugins-good needes to be removed
as these changes are already included in 1.16.1
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
This commit updates the imx-gpu-viv to the next version.
It includes the following improvments and fixes
* The work-around that moves .so for OpenCL, OpenVX, and Vulkan
to the main packages triggers the QA Issue for dev-so:
ERROR: imx-gpu-viv-1_6.4.0.p2.4-aarch64-r0 do_package_qa:
QA Issue: non -dev/-dbg/nativesdk- package contains symlink .so:
libvulkan-imx path '/work/aarch64-mx8m-poky-linux/imx-gpu-viv/1_6.4.0.p2.4-aarch64-r0/packages-split/libvulkan-imx/usr/lib/libvulkan_VSI.so' [dev-so]
Suppress the QA check.
* Add versions for OpenCL, OpenVX, and Vulkan.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
This commit removes the mesa-gl_%.bbappend file because that latest version
of the recipe is available in the zeus branch of meta-freescale.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
Busybox's device manager mdev was originally meant to be set up by writing its
path to /proc/sys/kernel/hotplug before launching it, but that entry no longer
exists in Linux v5.4's procfs and mdev can be launched directly.
Since mdev is the element in the recovery initramfs that is in charge of
mounting all partitions where .swu packages can be found (update partition on
the eMMC/MTD, uSD and USB), checking for the existence of the hotplug entry in
the procfs before launching mdev in v5.4 was preventing the partitions from
being mounted, and causing all software updates to fail.
While at it, move the two second delay to before mdev is launched, so all
partitions can be mounted. Otherwise, some devices such as the USB might not
be ready when mdev is launched, causing its partition to not be mounted.
https://jira.digi.com/browse/DEL-7143
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This recipe was originally ported from the zeus branch of poky into the dey-2.6
meta-digi branch to support the pkcs11 feature in cryptoauthlib. Now that we've
migrated to zeus, the recipe is now duplicated and no longer necessary.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Starting with Linux v4.15, regulatory domains are no longer handled via CRDA,
but via the kernel and a flexible database instead. Said database is included
in the wireless-regdb-static package, which conflicts with the old
wireless-regdb package.
To accomodate for this new package, add CRDA as a dependency for ccimx6
platforms only, and incorporate wireless-regdb-static for the rest of the
platforms. Additionally, the ccimx6 kernel should inherit the
kernel_wireless_regdb .bbclass so the plaintext database is copied to the
kernel sources, but since we use the same recipe for all kernel versions and
ccimx6 platforms are not yet supported in zeus, omit this change for now.
Remove the package-base .bbappend, since only ccimx6ulstarter images include
that packagegroup and they require wireless-regdb-static, anyway.
By adding the regulatory database, we avoid delays when going to suspend,
caused by the kernel waiting for the database to appear.
https://jira.digi.com/browse/DEL-7133
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Revert partially commit 1fb65f08 ("qtbase: apply imxgpu2d patches to imx8mn
platforms as well"), since it was fixed in meta-freescale layer in the commit
626e271b ("qtbase: Add i.MX 8 configuration")
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Gstreamer package was updated to v1.16.2 in poky layer, so
we need to update the base files used in meta-digi.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Commit 9d4490a ("qtwayland: really use OpenGL ES 2 API for decoration blitter")
from meta-qt5 layer backports an upstream patch to Yocto 3.0 (Zeus), which
conflicts with the same patch integrated in meta-digi layer.
This commit removes the patch from meta-digi.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This commit backports the IEEE 802.11r support from the later version v1.20
and integrates it in NetworkManager v1.18 supported by Yocto 3.0 (Zeus)
https://jira.digi.com/browse/CC6UL-1110
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This commit integrates support for the IEEE 802.11r protocol to operate with
fast roaming networks.
https://jira.digi.com/browse/CC6UL-1110
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
With the change of bsp now we have several entries under
/sys/bus/nvmem/devices/ in the CC6UL platform and we should
reduce the num of folders where the otp folder can be found.
ls /sys/bus/nvmem/devices/
bootloader
environment
imx-ocotp0
linux
recovery
rootfs
safe
update
https://jira.digi.com/browse/DEL-7082
Signed-off-by: Francisco Gil Martinez <francisco.gilmartinez@digi.com>
MMC core block has changed in kernel 5.4 so Replay Protected Memory Block (RPMB)
and boot partitions are not listed under /proc/partitions anymore.
get_emmc_block_device() function in pkg_postinst_ontarget() method was looking
for these entries to identify the MMC partition where to execute resize2fs.
This function has been modified to do the checks inside /dev/mmcblk* where RPMB
and boot entries are still listed.
https://jira.digi.com/browse/DEL-7094
Signed-off-by: Hector Bujanda <hector.bujanda@digi.com>
This allows to generalize the code instead of needing to replicate
overrides for each platform that contains the MCA.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
Based on commit ed2c4974 ("imx-gpu-viv: remove wayland as a requirement for
i.MX8 platforms"), this commit removes the requeriment of wayland as a backend
for the i.MX8 platforms to build framebuffer images.
https://jira.digi.com/browse/DEL-7013
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Commit 3418d1326c ("populate_sdk_base: provide options to set sdk type")
in poky layer introduces a new mechanism to create different archive types
for the sdk, and the function tar_sdk was renamed to archive_sdk.
This commit updates the custom SDK_POSTPROCESS_COMMAND variable with the new
function name.
https://jira.digi.com/browse/DEL-7013
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
There is a mismatch between the new upstream recipe that uses a cache folder
to share the header files and the imx recipe that requires a specific folder.
https://jira.digi.com/browse/DEL-7013
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Bluetooth class to support the bluez4/bluez5 distro features,
was removed due to bluez4 was removed from meta-oe some time ago.
This commit simplifies the requeriments adding directly the bluez5,
instead of the intermediate bluetooth class.
https://jira.digi.com/browse/DEL-7013
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Commit 07d4a6ba ("xserver-xorg: Backport to fix X server 1.20.1 crash")
integrates this patch in meta-freescale layer, then it is no longer
necessary to have it in our meta-digi layer.
This reverts commit 995212a213.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This configuration is required to sign and encrypt U-Boot images during
build time, as it is done for ccimx6ul platform.
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
This commit adds a installation script that uses fastboot support to
update the target firmware.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-6845
Additionally:
- The handling of gpios has been swapped so 'Set low XBEE_SLEEP_RQ' is done
before 'Power cycle XBEE_RESET_N' to assure the device doesn't enter sleep mode.
- Removed ExecStop entry from systemd service since it's doing nothing.
https://jira.digi.com/browse/DEL-6424https://jira.digi.com/browse/DEL-6423
Signed-off-by: Hector Bujanda <hector.bujanda@digi.com>
This interface should be the last item defined in the
/etc/network/interfaces file.
When you try to enable the interface br0 (bridge interface),
all the other interfaces should be available.
If the br0 interface is located before the other interfaces
involved in the bridge, it will fail.
Signed-off-by: Francisco Gil <francisco.gilmartinez@digi.com>
Digi Embedded Yocto 2.6-r3.1
Manually changed recipes to use the master branches instead of the fixed SHA1
from the last release.
Signed-off-by: Mike Engel <mike.engel@digi.com>
Environment encryption is not yet supported in U-Boot.
Unset TRUSTFENCE_ENCRYPT_ENVIRONMENT on the machine configuration
and remove the platform conditional on the class.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
* prefix TRUSTFENCE_ to variable SIGN_MODE for DEY
* prefix CONFIG_ to variable SIGN_MODE for script
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
The poweroff command is not available in the initramfs due to a missing
sysvinit/systemd dependency. Use the busybox "halt" command, since it's
available regardless of the init manager used. Rework the error message and
script variables accordingly.
https://jira.digi.com/browse/DEL-6983
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Some configuration files inside of the SDK make use of the default SDK
installation path, so some tools might break unless the SDK is installed in said
default path.
Recently, we modified the default installation path to include the platform and
the image type, but the image type was added after the SDK was created, so even
though the environment script's paths include the image type, the "original"
default path in the config files inside of the SDK doesn't include the image
type. A side effect of this is that Qt5 apps cannot be built, since the qmake
and Qt configuration files are pointing to the "original" SDK path.
Remove the image type from the path so that the paths in the SDK's config files
match the real default installation path.
This partially reverts commit be0fe088e3.
https://jira.digi.com/browse/DEL-6972
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
XBEE_RESET_N_GPIO and XBEE_SLEEP_RQ_GPIO can now be comma-separated lists of
GPIO indexes instead of just a single index. Modify the xbee-init script to
support this change and modify the sed script in xbee.bb to allow commas
in the aforementioned variables.
https://jira.digi.com/browse/DEL-6887
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>
Some .bbappend files for clutter, cogl and mesa recipes are already available
in meta-freescale, so we can remove them from meta-digi. Also remove the
libinput recipe, since a much newer version of it exists in poky.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Userspace firmware loading support is required for the Linux imx-sdma driver.
The patches that accomplish this were originally in poky, but were removed in
the thud upgrade. Re-work the patches so they apply over systemd v239.
https://jira.digi.com/browse/DEL-6932
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Otherwise, examples such as skeletalanimation are broken.
Reported-by: Alfonso Martin Rey <alfonso.martinrey@digi.com>
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Update SRCBRANCH in most recipes and SRCREV for gstreamer1.0-plugins-good.
update imx-gst1.0-plugin to v4.5.2.
https://jira.digi.com/browse/DEL-6932
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Update SRCBRANCH in most recipes and SRCREV for gstreamer1.0-plugins-good.
update imx-gst1.0-plugin to v4.5.0.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Some architectures like i.MX8M Nano don't have imxgpu2d but still need
some of the Gstreamer plugins.
For example, gstreamer1.0-plugins-bad-meta provides the xwayland sink which
would otherwise not be available for platforms without gpu2d.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
Serial support to XBee cellular devices is deprecated since
the recommended communication protocol is USB, so we remove
the udev rules that supported these devices.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This dependency was originally removed in commit
eafa8684a3, but it was erroneously put back in
commit 793e901678 when updating the recipe using
the one in meta-fsl-bsp-release as reference.
Instead of removing the line containing the dependency, in order to avoid the
same situation from happening in the future, comment it out and add an
explanation about why we're removing it.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The .bbappend file in meta-freescale only applies these patches to platforms
with imxqpu2d, but they are necessary to build framebuffer images for the
ccimx8mn. Using the same approach as NXP in meta-fsl-bsp-release (applying the
patches to imxgpu platforms) duplicates the patches for platforms that are both
imxgpu and imxgpu2d, so append them for imx8mn platforms exclusively.
While at it, remove a patch that is no longer necessary, since the latest
versions of qtbase already have the patch's change in them.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
These patches were copied from meta-fsl-bsp-release layer,
but with the latest versions throws a compilation issue with the
ccimx8mn platform. However the upstreamed patches works fine.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
WPA and P2P configuration files are basically the same between all
platforms, so we remove all duplicated files to use a common file
and modify it in the recipe logic.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The systemd class adds by default packages named ${PN} to the
SYSTEMD_PACKAGES variable, but in our case the package name is
'${PN}-init', so it needs to be added explicitly.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This package needs to be installed in the rootfs for the demos to work.
Reported-by: Alfonso Martin Rey <alfonso.martinrey@digi.com>
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
These classes needs to be inherited so the different init services
(sysv, systemd) execute the script on boot.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Otherwise there are QA check failures:
package imx-codec-test-bin requires librt.so.1, but no providers found in RDEPENDS_imx-codec-test-bin? [file-rdeps]
package imx-codec-test-bin requires libc.so.6(GLIBC_2.4), but no providers found in RDEPENDS_imx-codec-test-bin? [file-rdeps]
...
This is due to the 'imx-codec-test-bin' package containing NXP-provided
pre-built binaries that are compiled with GLIBC.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Clean up this warning on build:
python3-xbee: No generic license file exists for: MPL2.0 in any provider
Signed-off-by: Javier Viguera <javier.viguera@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>
The previous patch was outdated, but now that we have a working PKCS11 engine
and the cryptochip supports it, update the patch with the new engine info.
https://jira.digi.com/browse/DEL-6835
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is the version Microchip recommends to use in for the newer cryptoauthlib
with pkcs11 support. This recipe was backported from the zeus branch of
meta-openembedded.
https://jira.digi.com/browse/DEL-6826
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This package has not been supported since OpenSSL was updated to v1.1.x, and it
has been deprecated by Microchip.
https://jira.digi.com/browse/DEL-6826
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Added QtQuickControls package on framebuffer images for ConnectCore 6UL
platform to improve the user experience. It is not added to X11 images due
to size limitations.
https://jira.digi.com/browse/CC6UL-1108
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
In very rare cases, random services would hang when powering off the system,
causing the poweroff process to stall for 90 seconds before timing out the stop
job. To avoid this behaviour, minimize the effect of these random freezes by
decreasing the timeout.
The default services in our system take well under 15 seconds to stop
gracefully, so we can guarantee that a timeout will never happen under normal
circumstances.
https://jira.digi.com/browse/DEL-6794
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Otherwise, systemd will have to guess the PID of the service's main process.
It guesses right most of the time, but sometimes it chooses the PID of the
original pulseaudio process instead of the daemon that gets forked off. This
caused the daemon to stop immediately after starting, breaking other apps that
require the pulseaudio server to be running.
Since the PID file is created in a user-specific runtime directory (and the
service is meant for the whole system), modify the wrapper script to create
a symlink to the PID file in a place where it can be obtained by systemd.
https://jira.digi.com/browse/DEL-6795
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Digi Embedded Yocto 2.6-r2.2
Manually changed recipes to use the master branches instead of the fixed SHA1
from the last release.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Otherwise, systemd will have to guess the PID of the service's main process.
It guesses right most of the time, but sometimes it chooses the PID of the
original pulseaudio process instead of the daemon that gets forked off. This
caused the daemon to stop immediately after starting, breaking other apps that
require the pulseaudio server to be running.
Since the PID file is created in a user-specific runtime directory (and the
service is meant for the whole system), modify the wrapper script to create
a symlink to the PID file in a place where it can be obtained by systemd.
https://jira.digi.com/browse/DEL-6795
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The default service only starts once per non-root user. Add a service that
starts pulseaudio by default along with a wrapper script that sets the
necessary environment variables before launching the daemon.
https://jira.digi.com/browse/DEL-6746
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Use ifupdown variable 'p2p-network-id' to pass a WPA supplicant network
id, to pre-populate some parameters (SSID/passphrase) when creating the
group where this device is the GO.
Also replace go_intent=7 with the auto parameter. According to the
documentation:
"auto" can be used to request wpa_supplicant to automatically
figure out whether the peer device is operating as a GO and if so,
use join-a-group operation rather than GO Negotiation.
https://jira.digi.com/browse/DEL-6741
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This commit fixes the error message when specific network scripts
are launched.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-6728
This was reported by the build:
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:
devtool modify <recipe>
devtool finish --force-patch-refresh <recipe> <layer_path>
This is the result of running the above commands to have
the patches automatically updated on their context lines:
devtool modify weston
devtool finish --force-patch-refresh weston meta-digi-dey
While on it, remove also the initial "From <SHA1>" lines.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
Add support for greengrass 1.9.2 and remove it for 1.9.0.
Support for 1.9.0 was never released and that version is
no longer available.
Signed-off-by: Francisco Gil <francisco.gilmartinez@digi.com>
The most current revision is incompatible with the v4.9 Linux UAPI. Reverting
to the previous commit of the imx-alsa-plugins repo reverts the UAPI changes
while keeping the same functionality, so use this revision for the ccimx6 and
ccimx6qp.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Latest meta-fsl-bsp-release tag 'rel_imx_4.14.98_2.1.0' replaces the
imx-alsa-plugins recipe from the meta-freescale upstream layer to fix
the build with the kernel 4.14. The commit cde60d6 ("asrc_pair: update
according to latest mxc_asrc.h") fixes the build issues.
https://jira.digi.com/browse/DEL-6732
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Trustfence is not yet fully supported for the CC8X.
Retore the warning.
This reverts commit 78534ca779.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
Update SRCREV and SRCBRANCH in most recipes. Update imx-gst1.0-plugin to
v4.4.7.
https://jira.digi.com/browse/DEL-6722
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Change the recipe name to an older version (v6.2.4.p1.8). This is done because
there haven't been any changes in the source code since said version.
https://jira.digi.com/browse/DEL-6722
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Update to v6.2.4.p4.2. Make sure to keep the "wayland" distro feature check
out of the recipe to be able to compile framebuffer images for the ccimx8x.
https://jira.digi.com/browse/DEL-6722
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The correct recipe that need to be used is located at
meta-digi-dey/recipes-qt/demo-extrafiles/
removing all the QT applications that are not included anymore in
rootfs.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-6690
This commit enables gstreamer support when built qtmultimedia. Also
sets the gstreamer plugin video source for QT.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-6691
Otherwise, users that are behind corporate firewalls might not be able to
obtain the package sources.
https://jira.digi.com/browse/DEL-6663
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This way, we assure that the openssl binary is included in the rootfs whenever
the base openssl package is included.
https://jira.digi.com/browse/DEL-6710
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Remove the 'mstructure-size-boundary' flag. This flag is not supported in
ARM64 toolchains, and without it the fbtest application works fine.
https://jira.digi.com/browse/DEL-6498
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
Commit c6e963f9e ("lvm2: Add RDEPEND on lvm2 to lvm2-udevrules")
in meta-oe layer added a package dependency for lvm2. This dependency
includes many unnecessary packages like lvm2, lvm2-scripts, etc.
and their dependencies that increase the size of the initramfs image.
Since lvm2-udevrules is not necessary for our initramfs image,
this commit removes the RRECOMENDS.
https://jira.digi.com/browse/DEL-6701
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Commit 074e3ba3 ("meta-digi-dey: add cryptsetup tool into initramfs") added
the runtime dependency to cryptsetup for all platforms, but it is
required only to encrypt/decrypt block devices.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This commit disables file system check on the root file system when it is encrypted.
This prevents the service from failing on encrypted rootfs with the message:
[FAILED] Failed to mount /run/media/mmcblk0p3.
See 'systemctl status run-media-mmcblk0p3.mount' for details.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-6655
The functionality provided by this bbappend is now available in meta-oe
upstream, commit 7f17da154372b5ec33947766783444961e8aa67c.
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@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.
The artifacts that must go inside the installer ZIP image are not anymore
the ones in UBOOT_CONFIG. For CC8X, the artifacts are combinations of
UBOOT_CONFIG and RAM_CONFIGS.
This commit adds a function 'get_bootable_artifacts()' to boot-artifacts class
to generate a new variable BOOTABLE_ARTIFACTS with the list of bootable
artifacts DEY produces.
The installer recipe can then simply iterate on that list, rather than
needing to calculate it by itself.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6641
A variable called IMAGE_BOOTLOADER was being used without distinction for
referring to two different things:
- the recipe that builds the bootable artifacts
- the prefix of those artifacts
The value of this is "u-boot" for most platforms, but "imx-boot" for the
CC8X based platforms.
The name of the variable is misleading, so this commit splits it into two:
- BOOTLOADER_IMAGE_RECIPE, to refer to the recipe
- UBOOT_PREFIX, to refer to the prefix of the bootable artifact
With the separation, the variable UBOOT_SYMLINK becomes a generic formed
one, so it is moved to digi-defaults.inc.
While on it, fix the image_types_digi.bbclass which was not making use of
the original variable to establish all the dependencies.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
This commit exports several internal headers and libraries
to allow link against them in user applications.
https://jira.digi.com/browse/DEL-6649
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
These packages are included in ccimx6/6qp/6ul images because they are a part of
packagegroup-core-x11-sato, which isn't included in ccimx8x images. To assure
that pulseaudio always gets included in non-fb images, add it as a dependency
in packagegroup-dey-audio.
https://jira.digi.com/browse/DEL-6464
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Since the original .bb file is already in the meta-digi layer, bitbake will
look inside of the bluez5-5.41 folder by default, so this line isn't needed.
https://jira.digi.com/browse/DEL-6448
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This commit modifies the weston ini file to support a custom
background and includes a new one with Digi branding.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Modify bluetooth init script to use kernel module to power on/off
the bluetooth chip instead of managing it directly from sysfs.
https://jira.digi.com/browse/DEL-6615
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
These icons have never been included in the filesystem until a recent commit in
poky (522b0d8615cdc6645f6dc37a03ea7584f19c7bfc). In total, they take up over
1 MiB and have been causing filesystem tests to fail on the ccimx6ul due to low
space.
Add a .bbappend to undo the commit's changes in our layer.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This fixes the problem of shell console returning to the login prompt
after a successful login.
Signed-off-by: David Escalona <david.escalona@digi.com>
To avoid possible conflicts with NetworkManager, remove systemd-networkd
entirely.
https://jira.digi.com/browse/DEL-6610
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
-p : Test the standard periodic interrupts (uses timers, doesn't wake from low power)
-u : Test the standard 1 Hz interrupt (uses RTC ALARM)
-v : Test MCA periodic interrupts (uses RTC PERIODIC_IRQ)
-w : Test MCA 1 Hz interrupt (uses RTC 1HZ)
https://jira.digi.com/browse/DEL-6602
Signed-off-by: Hector Bujanda <hector.bujanda@digi.com>
The Replay Protected Memory Block (RPMB) is an special storage
partition that cannot be accessed via standard block layer.
When a user space tool like blkid, tries to read it the kernel
suffers buffer I/O errors and timeouts.
This commit modifies the post installation script to filter the RPMB
partitions from the mmc block devices, to avoid multiple kernel
errors during the script execution.
https://jira.digi.com/browse/DEL-6609
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Removed the platform dependency to apply the resize to all platforms.
https://jira.digi.com/browse/DEL-6609
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The Replay Protected Memory Block (RPMB) is an special storage
partition that cannot be accessed via standard block layer.
When a user space tool like blkid, tries to read it the kernel
suffers buffer I/O errors and timeouts.
This commit modifies the post installation script to filter the RPMB
partitions from the mmc block devices, to avoid multiple kernel
errors during the script execution.
https://jira.digi.com/browse/DEL-6609
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Removed the platform dependency to apply the resize to all platforms.
https://jira.digi.com/browse/DEL-6609
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This recipe is an example for customer for a system-monitor. Scripts that
verify the system status can be added to /etc/system-monitor.d
The recovery mechanisms can be implemented on those scripts or in the
system-monitor script. The software watchdog systemd support is used to
guarantee that the system-monitor is running.
When using this it is recommended to enable the systemd hardware watchdog
support, refer to the systemd documentation for this.
The systemd service provided by this recipe is not enabled by default as it
is an example that needs customization.
https://jira.digi.com/browse/DEL-6593
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
Also create the folders that contain the scripts attending each
dispatch event type.
https://jira.digi.com/browse/DEL-6575
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Instead of the 20 seconds hardcoded currently in the code, allow to
configure the response timeout in the connectivity section of the main
NetworkManager config file.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Currently in a systemd based init, the httpd server is not launched. A
systemd service is needed, so add it.
Also install a CGI script that allows to use the device for the
NetworkManager connectivity check.
https://jira.digi.com/browse/DEL-6577
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This recipe is an example for customer for a system-monitor. Scripts that
verify the system status can be added to /etc/system-monitor.d
The recovery mechanisms can be implemented on those scripts or in the
system-monitor script. The software watchdog systemd support is used to
guarantee that the system-monitor is running.
When using this it is recommended to enable the systemd hardware watchdog
support, refer to the systemd documentation for this.
The systemd service provided by this recipe is not enabled by default as it
is an example that needs customization.
https://jira.digi.com/browse/DEL-6593
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
Also create the folders that contain the scripts attending each
dispatch event type.
https://jira.digi.com/browse/DEL-6575
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Instead of the 20 seconds hardcoded currently in the code, allow to
configure the response timeout in the connectivity section of the main
NetworkManager config file.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Currently in a systemd based init, the httpd server is not launched. A
systemd service is needed, so add it.
Also install a CGI script that allows to use the device for the
NetworkManager connectivity check.
https://jira.digi.com/browse/DEL-6577
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
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>
This is the version used in meta-fsl-bsp-release branch sumo-4.14.98-2.0.0_ga.
https://jira.digi.com/browse/DEL-6603
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is the version used in meta-fsl-bsp-release branch sumo-4.14.98-2.0.0_ga.
Change the .bbappend name so it's compatible with all versions of the package.
https://jira.digi.com/browse/DEL-6603
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is the version used in meta-fsl-bsp-release branch sumo-4.14.98-2.0.0_ga.
Change the .bbappend name so it's compatible with all versions of the package.
https://jira.digi.com/browse/DEL-6603
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is the version used in meta-fsl-bsp-release branch sumo-4.14.98-2.0.0_ga.
https://jira.digi.com/browse/DEL-6603
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is the version used in meta-fsl-bsp-release branch sumo-4.14.98-2.0.0_ga.
The code revision is exactly the same as the one in v6.2.4.p2.3, so simply
rename the recipe and delete files that are not necessary anymore.
https://jira.digi.com/browse/DEL-6603
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is the version used in meta-fsl-bsp-release branch sumo-4.14.98-2.0.0_ga.
https://jira.digi.com/browse/DEL-6603
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is the version used in meta-fsl-bsp-release branch sumo-4.14.98-2.0.0_ga.
Instead of having one common .inc file and one .bb file per architecture,
we now have one common .bb file for both architectures.
https://jira.digi.com/browse/DEL-6603
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is the version used in meta-fsl-bsp-release branch sumo-4.14.98-2.0.0_ga.
https://jira.digi.com/browse/DEL-6603
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is the version used in meta-fsl-bsp-release branch sumo-4.14.98-2.0.0_ga.
https://jira.digi.com/browse/DEL-6603
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The watchdog and ADC devices were not being modified to belong
to 'digiapix' group, so the examples did not run properly when
ran as a user different than root.
Reported-by: Andreas Burghart <andreas.burghart@digi.com>
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6581
This patch is included in the rocko and sumo branches of poky to avoid errors
when starting an xserver using DRI, but it was removed in the thud branch in
favor of newer input methods other than SIGIO. SIGIO is still supported, but
not explicitly in the xserver configuration.
Since the vivante driver on the i.MX6 is using DRI and, by extension, SIGIO
(even though there is no way to configure xserver to enable SIGIO support), the
only way to make xserver start correctly is by removing the SIGIO support check
in the code.
https://jira.digi.com/browse/DEL-6565
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Even though systemd support is not yet available for these platforms, add the
scripts so bitbake doesn't fail when building the busybox package.
https://jira.digi.com/browse/DEL-6565
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
* Use the same operation order when resuming interfaces
* Remove unnecessary delay in ccimx6sbc standby script
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Otherwise, bitbake will try building the aarch64 version of the package and
fail when building ccimx6 images.
https://jira.digi.com/browse/DEL-6565
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Digi Embedded Yocto 2.6-r1.3
Manually changed recipes to use the master branches instead of the fixed SHA1
from the last release.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The exported PWM channels now report the channel name under udev
EXPORT parameter.
Add the 'change' udev action type to the udev rules and use that
parameter to change the group ownership of the PWM channels to
digiapix group, so they can be used by non-root user.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
For some reason, even though the general RDEPENDS for this package is correct,
all items are overwritten by the empty class-native version of RDEPENDS, even
when building for the target. Because of this, whenever this python module is
installed and used, it won't work.
Redefine the dependencies needed by the target until the issue is fixed
upstream.
https://jira.digi.com/browse/DEL-6553
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Some modems take a lot of time to initialize and ModemManager won't
see them on its first scan.
This service will force a rescan 40 seconds after boot, to give
enough time for those lazy modems.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6366
This recipe adds a script and a related systemd service that
configures two GPIOs (user defined, or else platform-defaults) as
output and sets them to the appropriate value for initializing the
XBee socket:
- XBEE_SLEEP_RQ: is set low, for running the XBee
- XBEE_RESET_N: is set low and then high, to reset the XBee
The service triggers on the condition that the UART TTY device node
pointed to by variable XBEE_UART exists.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6366
On the default device tree, the MCA UART that's connected to the
XBee socket is enabled. This registers as ttyMCA0.
Add a udev rule for this path so that ModemManager checks for
modems in this serial port.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6366
With the re-organisation of the python3 packaging, some of the
packages have disappeared and are now part of base packages.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Otherwise, packagegroup-dey-core won't get included in ccimx6ulstarter images.
This packagegroup contains fundamental OS elements, such as sysvinit, kernel
modules and so on. Use CORE_IMAGE_BASE_INSTALL instead and make sure to append
to the default value instead of overwriting it.
https://jira.digi.com/browse/DEL-6536
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
For CC6/CC6Plus
- Add USER_LED0 alias (same as default USER_LED)
- Change aliases of the other LEDs to USER_LED1 and
USER_LED2 (without additional underscore and fixed
indexes, to match the board schematics)
For CC8X SBC Pro
- Add USER_LED0 alias (same as default USER_LED)
- Add USER_LED1 which was missing
- Increase indexes (due to removed MCA_IO19 on SOM v3)
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
This modifies the behavior of the sd-resolve libsystemd component to prevent
the system from freezing whenever a service that uses said component is
stopped. Even though this doesn't free the terminated thread's resources
properly, this procedure only gets executed during the final moments of a
service's process before it exits, so resource leaks aren't an issue.
https://jira.digi.com/browse/DEL-6523
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This commit removes the following examples that were accessing
hardware interfaces:
- dey-examples-adc
- dey-examples-can
- dey-examples-gpio-sysfs
- dey-examples-spidev
- dey-examples-watchdog
The recipe 'dey-examples-digiapix' builds similar examples that make
use of Digi's APIX for accessing the hardware. Add this recipe to images
- dey-image-qt
- core-image-base
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-5169
This reduces the number of files that must be modified when changing
branches between development/release modes.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
Organize the common code in the recipe to make easy the
inclusion of new greengrass versions.
Signed-off-by: Francisco Gil <francisco.gilmartinez@digi.com>
This way, the wlan1 interface will only be created whenever a user wants to
bring the interface up with ifupdown. Modify the script to be able to delete
the interface whenever it gets brought down and remove its .sh file extension
so run-parts can run it properly during the ifup process.
https://jira.digi.com/browse/DEL-6353
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Tests have shown that having this interface up hinders wlan0's performance,
so don't bring it up by default.
https://jira.digi.com/browse/DEL-6353
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>
The device-tree being used on a system is a very important piece of
information to debug issues. On a host machine, dtc can be used to
reconstruct the DTS used from the /proc/device-tree folder structure.
While on it, remove extra white lines at the beginning and end.
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
This script introduces a minor delay when the own script
launch the wpa_supplicant daemon, however this minor delay
is needed in the boot process when the wireless interface
is loaded, if not the bridge mechanism throws an unexpected
error trying to add the interface to the bridge before the
wireless is ready to use.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Since our initscript contains logic to dynamically generate the path containing
the greengrass daemon (it changes depending on the version), keep it in the
rootfs. Create a symlink to it inside of /etc/init.d for sysvinit images and
create a systemd service wrapper that calls it on systemd images.
https://jira.digi.com/browse/DEL-6510
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Soften the dependencies between the services and start the bluetooth stack
regardless of the existence of a bluetooth chip. Also, update the standby
script to reflect that there is no longer a strong dependency between the
services.
https://jira.digi.com/browse/DEL-6452
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Unlike eudev, which is used on images without systemd, the list of paths
systemd-udev uses to look for rules is very limited. Include an upstream patch
(commit 116b91e8ccfee1d44fc2b140d831d688e3747902 in the systemd repo) that
expands said list.
This fixes an issue with crda's regulatory domain rule file, which was being
excluded due to it being in a path systemd-udev was ignoring (/usr/lib/udev).
Because of this, the regulatory domain was never set properly and hostapd was
failing when configured to use 5GHz channels (which is the default config).
https://jira.digi.com/browse/DEL-6504
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
To avoid bringing up interfaces before they're created by udev scripts
(specifically wlan1), wait until udev settles before starting the service.
https://jira.digi.com/browse/DEL-6504
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
When using systemd, putting the wlan1 interface up wasn't working because it
was relying on initscripts that are no longer in the filesystem.
Add a parametrized version of the upstream hostapd service to be able to use a
configuration that's different from the default one. Also, modify the
generation of the wlan1 entry in /etc/network/interfaces to be able to use
different post-up/pre-down hooks depending on the init manager that's being
used.
https://jira.digi.com/browse/DEL-6504
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This change was added to meta-openembedded layer by commit
0814df2e9179b71b5f5c99b962aca35ede1f242f.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Since the version 1.12, NetworkManager enables the colors in the
terminal output by default. This pretty output is not compatible
with several terminal emulators and makes it difficult to parse
the output of the CLI commands.
This patch uses the standard linux util called 'terminal-colors.d'
to disable the colors by default in the NetworkManager CLI interpeter.
https://jira.digi.com/browse/DEL-6473
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Latest update to version 1.29.3 in upstream breaks the compatibility
of our bbappend, to avoid it in future updates, this commit
generalizes the bbappend to apply all the 1.29 series.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Add pulseaudio audio profile for MAX98089 sound card and
generalize the recipe to support multiple platforms with
the same audio sound card.
https://jira.digi.com/browse/DEL-6461
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The driver now builds directly from the kernel source and the
fixes are already included in the kernel tree so there is no need
to build the module externally.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6460
(cherry picked from commit a0990a7e1dcd03af239efb620b83b7dee126484e)
This is a user space tool to manage BATMAN advanced network interfaces.
https://jira.digi.com/browse/DEL-6466
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
systemd-tmpfiles throws warnings of /var/run being deprecated in favor of /run.
Even though this is corrected automatically, the warnings appear several times
during runtime, polluting the systemd journal.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Similar to what we did on sysvinit, stop dnsmasq from starting automatically
on boot so NetworkManager can launch it via dbus.
https://jira.digi.com/browse/DEL-6415
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The postinst script tries parsing the wireless MAC address from the sysfs, and
in case of failure, obtains a random string from /dev/urandom. This caused two
problems when booting with systemd:
* The wifi interface's sysfs entry is not available because the interface
hasn't had time to start up yet, forcing the script to always resort to the
/dev/urandom fallback.
* Even though the postinst scripts are run after populating the volatile
filesystems (as can be seen in run-postinsts.service's dependencies), trying
to read either /dev/random or /dev/urandom at this point in the system's
initialization causes it to lock up indefinitely.
To avoid either situation, add the following changes:
* Immediately exit when running on a non-wireless target, as the script isn't
necessary in this use case.
* Parse the wireless mac address from /proc/device-tree/wireless, which is
guaranteed to always be available when the script runs. By doing this, we can
remove the /dev/urandom fallback entirely.
https://jira.digi.com/browse/DEL-6415
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This script behaves the same way as our custom standby script, with a few
modifications, for example:
* instead of using initscripts to stop/start daemons, it uses systemctl calls
* save variables that are needed when resuming in /tmp, because the script is
executed twice instead of once (when suspending and when resuming)
* remove the locking/unlocking of the critical section and the actual state
change, since that is handled by systemd-suspend now
Also, add a different standby script for when systemd is enabled. Said script
acts as a wrapper for systemd's suspend mechanism.
https://jira.digi.com/browse/DEL-6415
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
These changes are needed in order to achieve a behavior similar to our
bluetooth initscripts'.
https://jira.digi.com/browse/DEL-6415
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This service acts as a systemd replacement for our bluetooth-init initscript.
All it does is call the initscript before starting the bluetooth stack.
Since initscripts dissapear from /etc/init.d when disabling sysvinit, move the
script to /etc/. Also, include bluez5-init as a packagegroup-dey-bluetooth
dependency regardles of whether systemd is enabled or not.
https://jira.digi.com/browse/DEL-6415
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
These patches don't apply on the latest version of systemd used in Yocto 2.6.
https://jira.digi.com/browse/DEL-6415
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Without systemd, our KEY_POWER events were handled by the ACPI daemon, which in
turn issued a "poweroff" command. With systemd, the ACPI daemon is no longer
available and the events are handled by systemd-logind instead, which also
powers down the system properly. However, NXP added a patch that prevents
system-logind from handling the events, since they use the sc_powerkey instead.
Remove this patch to be able to power the target off via our power button.
https://jira.digi.com/browse/DEL-6415
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Otherwise, there will be errors due to missing dependencies.
https://jira.digi.com/browse/DEL-6415
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
These have been ported directly from NXP's meta-fsl-bsp-release layer.
https://jira.digi.com/browse/DEL-6415
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Since poky commit b6fbb3f3d4d6367b0fd7921078f67057551c7ede
reboot config was moved to init.cfg to provide this configuration
when busybox is selected as the init manager, however it is needed
for initramfs images where no init manager is set (see poky commit
ef4a417ab04779bd9fc8a6540a20cca7d14e98cf).
https://jira.digi.com/browse/DEL-6451
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Since commit 4b41d9072a304fadbe1cc37c94575f12a2a47fd3 in poky
busybox removes the RRECOMENDS dependency with busybox-syslog,
then we need to explicitly add this dependency in the recipes.
https://jira.digi.com/browse/DEL-6443
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Remove git recipe to use the official 1.8.2 release and update
udev rules file to blacklist the network interfaces that ModemManager
must not manage.
https://jira.digi.com/browse/DEL-6412
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Commit 491082c56ce34f3fd644f8d4457ccd52af951087 in poky layer enables
by default some security enhancements and optimizations for the compiler,
These extra checks added by the flag -D_FORTIFY_SOURCE=2 break the
CloudConnector build. This commit disables the extra validations only
for the CloudConnector recipe.
https://jira.digi.com/browse/DEL-6412
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Removed patches already integrated in the OpenSSL code and
refreshed the necessary ones.
https://jira.digi.com/browse/DEL-6412
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Wireless tools is deprecated in favor of iw because the
wireless extensions have been deprecated in favor of the
new nl80211 interface for wireless devices.
https://jira.digi.com/browse/DEL-6412
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The defconfig file has been refreshed for the current busybox
version 1.29.2 maintaining the same applets enabled.
https://jira.digi.com/browse/DEL-6412
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This script was added a long time ago and it never gets used anymore, so remove
it from our images.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The point of this recipe is to provide the version of Bluez5 that was
certified. Thes certification does not apply to the ConnectCore 8X, and the
recipe currently fails to build due to missing files. Hence filter out the
ConnectCore 8X from this recipe.
This clears the following warnings:
WARNING: meta-digi/meta-digi-dey/recipes-connectivity/bluez/bluez5_5.41.bb: Unable to get checksum for bluez5 SRC_URI entry bluetooth-init: file could not be found
WARNING: meta-digi/meta-digi-dey/recipes-connectivity/bluez/bluez5_5.41.bb: Unable to get checksum for bluez5 SRC_URI entry main.conf: file could not be found
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
(cherry picked from commit bf9688fd08ac9e8823a5a253bdd1acacd1c0870e)
Trustfence is not supported in the CC8X at the moment. This cleans the
following warning:
WARNING: meta-digi/meta-digi-dey/recipes-core/trustfence/trustfence-initramfs.bb: Unable to get checksum for trustfence-initramfs SRC_URI entry trustfence-initramfs-init: file could not be found
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
(cherry picked from commit 778fc424274fc0983c348f4da6ca09e1a7b5b859)
vpx was wrongly removed when updating the recipe to version 1.14, but it's
required to build x11 images for the ccimx6ulsbc.
https://jira.digi.com/browse/DEL-6078
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
(cherry picked from commit 1e2244afcd)
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
CC8X SBC Pro's LPUART0 port is routed to the Expansion connector.
The UART located in the XBee socket, MCA UART, is not currently supported
so comment the XBee Cellular rule for the moment.
https://jira.digi.com/browse/DEL-6417
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
The defconfig file has been refreshed for the current busybox
version 1.27.x maintaining the same applets enabled.
Signed-off-by: Arturo Buzarra <arturo.buzarra@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>
Digi Embedded Yocto 2.4-r2.2
Manually changed recipes to use the master branches instead of the fixed SHA1
from the last release.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
qt3d sometimes fails to build due to an upstream issue that has yet to be
resolved. Since this interferes with our daily builds from time to time, remove
qt3d from our images completely.
https://jira.digi.com/browse/DEL-6348
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
SOM v1 is not going to be released, so there's no need for a revision check.
Now that hw flow control is available, use it along with the highest baudrate
possible.
This reverts commit e4fbba3dde.
https://jira.digi.com/browse/DEL-6254
Our current OpenSSL libraries are only functional when applications link
against v1.0.2d or higher, making some packages containing pre-compiled
applications that link to older versions (like AWS Greengrass) fail to build
and/or run properly.
This commit includes:
* Changing SHLIB_EXT from so.1.0.2 to so.1.0.0
* Reverting the version-script to an older version with backwards
compatibility plus newer symbols
Specifically, these changes partially revert the patches added in the poky
layer's commits a59bfd05d15085a3dc5669b47fd19867246c846b and
73a43fc15e0463c39baaadecab78fb3ef51b8cd0 respectively.
Please note that this only modifies the cryptographic library's ABI, its code
remains unchanged.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The PWM and ADC values are still to be determined, since their BSP support is
currently unavailable.
https://jira.digi.com/browse/DEL-6205
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Initialize Bluetooth chip in HCI_H4 mode and provide a firmware binary
with the IBS and DEEP_SLEEP mode disabled by default. Also this firmware
enables an internal clock required to maintain the system on low power modes.
https://jira.digi.com/browse/DEL-3711
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The Digi vendor kernel uses a dedicated HCI UART driver with support for
In-Band Sleep (IBS). This driver, when used with a QCA vendor ROME plugin
for hciattach, is able to upload a new firmware version to the Bluetooth
chipset, as well as set the MAC address directly on the firmware.
Mainline BSP uses the HCI H4 driver instead and the "qualcomm" hciattach
plugin which is not able to upload firmware to the QCA6564 chipset.
As such, when using mainline the chipset uses the ROM firmware and the
bluetooth init script has been adapted accordingly.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The meta-freescale layer assumes that when you define the use-mainline-bsp
the platform is going to use the etnaviv gpu driver. This is not the case
for the CC6UL as the mxsfb.c driver is still not DRM capable.
Probably this will change in v4.19 as there is a DRM capable mxsfb.c
driver that will make it possible to use the armada xf86 driver with the
etnaviv fbdev emulation.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
* Check for file before using it
This just avoids the failure, on mainline access to OTP would need to be
done differently, see:
https://jira.digi.com/browse/ACL-163
* Use compatible node instead of digi,machine,name
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Currently the contents of FILESEXTRAPATHS and the actual paths being used for
the patch files are not aligned. That generates the following WARNINGs:
imx-gst1.0-plugin_4.3.4.bb: Unable to get checksum for imx-gst1.0-plugin SRC_URI entry 0001-gstimxv4l2-map-dev-video1-to-dev-fb0.patch: file could not be found
kernel-module-imx-gpu-viv_5.0.11.p8.6.bb: Unable to get checksum for kernel-module-imx-gpu-viv SRC_URI entry 0001-mxc-gpu-use-recommended-values-for-minimum-GPU-frequ.patch: file could not be found
kernel-module-imx-gpu-viv_5.0.11.p8.6+fslc.bb: Unable to get checksum for kernel-module-imx-gpu-viv SRC_URI entry 0001-mxc-gpu-use-recommended-values-for-minimum-GPU-frequ.patch: file could not be found
Also, those patches are not being applied.
This patch fixes FILESEXTRAPATHS to contain the actual paths being used.
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
(cherry picked from commit 4d35d15fee)
Currently the contents of FILESEXTRAPATHS and the actual paths being used for
the patch files are not aligned. That generates the following WARNINGs:
imx-gst1.0-plugin_4.3.4.bb: Unable to get checksum for imx-gst1.0-plugin SRC_URI entry 0001-gstimxv4l2-map-dev-video1-to-dev-fb0.patch: file could not be found
kernel-module-imx-gpu-viv_5.0.11.p8.6.bb: Unable to get checksum for kernel-module-imx-gpu-viv SRC_URI entry 0001-mxc-gpu-use-recommended-values-for-minimum-GPU-frequ.patch: file could not be found
kernel-module-imx-gpu-viv_5.0.11.p8.6+fslc.bb: Unable to get checksum for kernel-module-imx-gpu-viv SRC_URI entry 0001-mxc-gpu-use-recommended-values-for-minimum-GPU-frequ.patch: file could not be found
Also, those patches are not being applied.
This patch fixes FILESEXTRAPATHS to contain the actual paths being used.
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
On this platform, the SPI device gets registered as /dev/spidev32766.0.
https://jira.digi.com/browse/DEL-6183
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
During the merge of the maintainance branch and the manual revert of
some recipes, these were forgotten.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
On this platform, the SPI device gets registered as /dev/spidev32766.0.
https://jira.digi.com/browse/DEL-6183
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The generate_installer_zip() function had a hardcoded "u-boot" filename when adding
the bootloader to the list of files that are put in the installer .zip.
https://jira.digi.com/browse/DEL-6174
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Set a lower baudrate of 115200bps for bluetooth on SOMv1 since
hardware flow control is not available.
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
These packages create dependency issues when compiling framebuffer images, and
they aren't essential. Include them only in ccimx6 images.
This reverts commit 2edb127d28.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The sources for this package do not exist anymore, causing the build to fail
unless said sources can be obtained via a mirror.
https://jira.digi.com/browse/DEL-6147
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Currently, it isn't possible to wake up the ccimx8x after suspending to RAM.
For now, use the less strict "freeze" low power mode instead.
https://jira.digi.com/browse/DEL-6148
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The recipe's contents are unchanged, but the version number in the recipe name
will now match the rest of the vivante-related recipes.
https://jira.digi.com/browse/DEL-6115
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The package is now available for download on NXP's mirror, so we can fully sync
our recipe with the one in meta-fsl-bsp-release.
https://jira.digi.com/browse/DEL-6115
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Also remove our .bbappend, since it's not needed anymore after updating our
machine overrides.
https://jira.digi.com/browse/DEL-6115
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
These packages are required for videos to play properly on the ccimx8x. Also,
add gstreamer1.0-libav explicitly since the only package that depends on it
(gst-player-bin) was removed from packagegroup-core-x11-sato.
https://jira.digi.com/browse/DEL-6026
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@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>
This is done in meta-fsl-bsp-release when building xwayland images, so port it
to our layer.
https://jira.digi.com/browse/DEL-6104
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This updates our Qt5 packagegroup with all of the packages included in NXP's
fsl-image-qt5-validation-imx.bb.
https://jira.digi.com/browse/DEL-6104
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This merges our Qt5 recipes with the ones in meta-fsl-bsp-release.
https://jira.digi.com/browse/DEL-6104
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
These recipes update Qt5, its plugins and adds wayland support.
https://jira.digi.com/browse/DEL-6104
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Some of these recipes might not be strictly necessary for xwayland to work, but
they are related, so I have added them just in case.
https://jira.digi.com/browse/DEL-6104
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
vpx was wrongly removed when updating the recipe to version 1.14, but it's
required to build x11 images for the ccimx6ulsbc.
https://jira.digi.com/browse/DEL-6078
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The newer version used for the ccimx8x has a different license, so its checksum
must be changed.
https://jira.digi.com/browse/DEL-6078
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This package depends on libg2d, and the latest version of this library's
sources for imx6 platforms are currently unavailable. Among other things, the
newer sources add a symbol needed by imx-gst1.0-plugin to compile, so this
patch manually adds the symbol as a macro in the package's source code.
https://jira.digi.com/browse/DEL-6078
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The aarch32 recipe will remain the same for now, since the newer sources aren't
yet available in NXP's mirrors.
https://jira.digi.com/browse/DEL-6078
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is the version used by NXP in the rocko-4.9.88-2.2.0_8qxp_beta2 branch of
their meta-fsl-bsp-release layer.
https://jira.digi.com/browse/DEL-6078
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The most important change here is the package's revision.
https://jira.digi.com/browse/DEL-6078
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is the version used by NXP in the rocko-4.9.88-2.2.0_8qxp_beta2 branch of
their meta-fsl-bsp-release layer.
https://jira.digi.com/browse/DEL-6078
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is the version used by NXP in the rocko-4.9.88-2.2.0_8qxp_beta2 branch of
their meta-fsl-bsp-release layer.
https://jira.digi.com/browse/DEL-6078
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This is the version used by NXP in the rocko-4.9.88-2.2.0_8qxp_beta2 branch of
their meta-fsl-bsp-release layer.
https://jira.digi.com/browse/DEL-6078
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
We now have different tarballs for each CPU architecture we compile for. Also,
add support for the aarch64 tarball.
https://jira.digi.com/browse/DEL-6046
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The PWM and ADC values are still to be determined, since their SOM support is
currently unavailable.
https://jira.digi.com/browse/DEL-6049
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The Display Processing Unit (DPU) on the i.MX8 is what NXP used to call
Image Processing Unit (IPU) on the i.MX6 family.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
Commit 15139a3e97 wrongly removed 'vpx' from plugins-good which
is needed to play WebM files on the CC6UL.
The packagegroup-dey-gstreamer also needed to be updated to use
'pulseaudio' from plugins-good which was apparently renamed from 'pulse'.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6029
(cherry picked from commit 29add13409)
adc_sample:
- extend list of supported devices with MCA_CC8X
adc_cmp_sample:
- Add '-t' argument to specify the type of device.
- Added checking of threshold ranges to avoid confusion between
raw and voltage configurations.
https://jira.digi.com/browse/DEL-6001
Signed-off-by: Hector Bujanda <hector.bujanda@digi.com>
Commit 15139a3e97 wrongly removed 'vpx' from plugins-good which
is needed to play WebM files on the CC6UL.
The packagegroup-dey-gstreamer also needed to be updated to use
'pulseaudio' from plugins-good which was apparently renamed from 'pulse'.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6029
- For most examples, since they apply to all platforms, remove
COMPATIBLE_MACHINE.
- For recipes related to specific hardware, add support to the new platform
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
While on it:
- add dey-examples-rtc unconditionally (rtc is never in MACHINE_FEATURES)
- add missing recipes: digiapix, cryptochip
- re-order them alphabetically.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
This commit:
- moves the files in platform folders 'ccimx6qsbc' and 'ccimx6ul' to the
recipe's folder (they are the same).
- moves the install instructions for virtual wlan and wlan1 into functions
that can be reused by both platforms.
- moves the bridge example install instruction to the generic do_install()
since it's the same for all.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
Commit 15139a3e97 removed all gstreamer plugins recipes
but NXP meta-fsl-bsp-release still contains .bbappends that
this commit re-adds.
Besides, the imx-gst1.0-plugin recipe contained a patch by Digi
that was also wrongly removed and that this commit re-adds without
the version on the filename.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6029
meta-freescale rocko branch now sources gstreamer and its plugins
from repositories in codeaurora that contain all patches, so these
recipes are no longer required in meta-digi.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6029
(cherry picked from commit 105ab7a89b)
Commit 105ab7a89b removed all gstreamer plugins recipes
but NXP meta-fsl-bsp-release still contains .bbappends that
this commit re-adds.
Besides, the imx-gst1.0-plugin recipe contained a patch by Digi
that was also wrongly removed and that this commit re-adds without
the version on the filename.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6029
This is taken from meta-fsl-bsp-release layer at branch 'rocko-4.9.88-2.0.0_ga'
at SHA1 d65692ecb3a4.
A *.bbappend is required to explicitly set COMPATIBLE_MACHINE.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6029
- These have been taken from meta-fsl-bsp-release layer at branch
'rocko-4.9.88-2.0.0_ga', SHA1 d65692ecb3a4.
- Old recipes have been removed.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6029
meta-freescale rocko branch now sources gstreamer and its plugins
from repositories in codeaurora that contain all patches, so these
recipes are no longer required in meta-digi.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6029
- The variable containing the list of patches has been renamed to a more
generic prefix QCA65XX_.
- The ConnectCore 8X uses GPIO3_10 (394) for BT_EN.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-5936
This is taken from meta-fsl-bsp-release layer at bb80ba5a0104.
The file had a few commented lines for Wayland that have been uncommented
to leave them untouched in the commit.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-5937
The commit 32a6e809f811e8b3920326330d8225b3dd895f70 from the poky layer
breaks the build in the maintenance branch for rocko. This patch updates
the curl base recipe to use the latest version.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The commit 32a6e809f811e8b3920326330d8225b3dd895f70 from the poky layer
breaks the build in the maintenance branch for rocko. This patch updates
the curl base recipe to use the latest version.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Manually changed recipes to use the master branches instead of the
fixed SHA1 from the last release.
Digi Embedded Yocto 2.4-r1.2
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
Firmware verification has a side effect in cc6ul sbc express platform
that affects to the bluetooth initialization.
https://jira.digi.com/browse/DEL-5802
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Whenever there's a big time jump due to an outaded RTC being updated via NTP,
detect the jump and update the DHCP lease's expiry times accordingly.
https://jira.digi.com/browse/DEL-5233
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
From python 2.x to python 3.x, the '/' operator changed from integer
division to float division.
Hence, when using one core, 'makejobs' was being evaluated to 0.5.
That caused the evaluation below (makejobs == 0) to return False (0),
therefore PARALLEL_MAKE was evaluated to '-j 0' and the compilation
failed because the 'j' parameter must be strictly postive.
Replace the operator by the integer div operator in python 3.x '//'.
https://jira.digi.com/browse/DEL-5769
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
With the migration from dey-2.2 to dey-2.4, now it is mandatory to include
all required applications for compilation. This fixes the next error:
| make: pkg-config: Command not found
| main.c:20:10: fatal error: cryptoauthlib.h: No such file or directory
| #include <cryptoauthlib.h>
https://jira.digi.com/browse/DEL-5710
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Rarely the bluetooth firmware is not loaded properly and causes
errors in the configuration steps. This verification makes sure
the firmware was loaded and is functional, if not we start the
retry mechanism with the default baudrate to avoid the firmware
corruption in the upload process.
https://jira.digi.com/browse/DEL-3711
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
With the switch to using Bash as command line interpreter, the default
/etc/inputrc configuration file for readline doesn't allow the use of
some keys which are common.
This commit enables them to not change the user experience with previous
DEY versions.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-5623
The suspend script has conflicts with the suspend from bash, then
we decided to rename our custom suspend script to standby and create
a symlink called suspend to maintain backward compatibility.
https://jira.digi.com/browse/DEL-5622
Signed-off-by: Arturo Buzarra <arturo.buzarra@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>
Option --reference does not exist for busybox chmod/chown, so you get an ugly
error and file rights are modified.
https://jira.digi.com/browse/DEL-5642
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Sync defconfig to enable command 'chvt' because the xserver-nodm
init script requires this command in the stop process to swicth
the foreground virtual terminal after stopping the xserver.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Xserver prints many debug messages by the console output,
this bbappend modifies the init line to redirect the messages
to a log file.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Sync defconfig to enable command 'command' because /etc/profile
of base-files requires this command to be available. If it is not
available the following message is output during login on a image
using busybox.
-sh: command: not found
(From OE-Core rev: e41c90b852167bbcb434da57b84280e855acae33)
https://jira.digi.com/browse/DEL-5632
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Bash v4.4 or higher warns when discarding NULL bytes in command substitution
output. Remove these bytes to avoid the undesired warnings.
https://jira.digi.com/browse/DEL-5588
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Currently the default bluez5 package installed is bluez-5.46, but we need this
locally for compiling bluez-5.41 (the stack using in the bluetooth
certification process), so we need to locally apply the same fix ("fix python3
core dependency for testtools") for the testtools and its dependency with
python3-code instead of python3.
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Adding the bluetooth testtools does not have a big benefit and increases the
size of the rootfs in 16MB given its dependencies, which is critical in
devices (CC6UL) with a NAND flash.
https://jira.digi.com/browse/DEL-5613
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Gabriel Valcazar
Arturo Buzarra
Hector Palacios
Francisco Gil
Mike Engel
Javier Viguera
Gonzalo Ruiz
Hector Bujanda
Mattias Lindblad
Jose Diaz de Grenu
David Escalona
Alex Gonzalez
Isaac Hermida