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>
Gonzalo Ruiz
Gabriel Valcazar
Arturo Buzarra
Mike Engel
Hector Palacios
Mattias Lindblad
Francisco Gil Martinez
Hector Bujanda
Javier Viguera
Jose Diaz de Grenu
David Escalona