Also clean some dead code: libjpeg-turbo is the only jpeg implementation
in poky since long ago. Also "remove-libtool" is enabled by default in
bitbake so there is no need to do it in our distro configuration.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The recipes have been updated in meta-freescale, and version 1.18.5.imx
is no longer available.
Follow same change in meta-freescale's "conf/machine/include/imx-base.inc".
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This fixes a failure in the firmware installation script when trying to
program crank images:
./install_linux_fw_uuu.sh -i dey-image-crank
[ERROR] Could not find file 'dey-image-crank-ccimx6ulsbc.boot.ubifs'
[ERROR] Could not find file 'dey-image-crank-ccimx6ulsbc.recovery.ubifs'
[ERROR] Could not find file 'dey-image-crank-ccimx6ulsbc.ubifs'
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
meta-freescale updated to version '10.0.0.imx', so our bbappend fails
with:
ERROR: No recipes in default available for:
... meta-digi-dey/dynamic-layers/freescale-layer/recipes-graphics/wayland/weston_9.0.0.imx.bbappend
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Also, fix the sequence number of the GPIO_SET_DEBOUNCE_IOCTL ioctl. Same
fix has been done in Linux.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
* fix arch tune files path in machine config
* update imx-digi-base config file (using as a base the imx-base.inc
config file in 'meta-freescale')
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
These variables were originally set in NXP's recipes, but they moved their
definitions to each platform's configuration file. Set the appropriate values
where needed. While at it, replace every mention of the SOC_TARGET variable
with its new name, IMX_BOOT_SOC_TARGET.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Other layers, such as meta-digi-dualboot, may add scripts to this
list on their layer.conf file. Depending on the order and priority
of layers, using a strict '=' here completely overrides previous
values, which is not desired.
Reported-by: Francisco Gil <francisco.gilmartinez@digi.com>
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
This is necessary for images that have SELinux enabled. Aside from changing
some package configurations and including an additional library in the rootfs,
this change has no apparent effects on the core functionality of the system.
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 package includes a script that is executed by a udev rule that we
currently include in our sysvinit images. Without it, the regulatory firmware
mechanism is broken and an error appears when booting the system.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Create global variables:
DEFAULT_IMAGE_NAME
GRAPHICAL_IMAGES
to have them substituted on the U-Boot install scripts for better
generalization.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
This version is only required to build U-Boot 2017.X, so since CC6UL was moved
to a new U-Boot version it is not necessary and also fixes a build issue.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Commit 4ab569fb("recipes-*: refine restrictions for NXP BSP") from
meta-freescale layer restrict the use of certain recipes and classes to
enforces them to use a NXP BSP. This is done by adding a new MACHINEOVERRIDES
called "use-nxp-bsp"
https://jira.digi.com/browse/DEL-7508
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Update the MACHINE values with the ones in meta-freescale and meta-imx layer.
https://jira.digi.com/browse/DEL-7397
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Since this component pulls in Optee dependencies, which in turn depend on
packages from meta-python2, add this layer to the ccimx8mn-dvk's default
bblayers.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-7025
Add the ccimx6/6qp and update the ccimx8x supported U-Boot version. Even though
older versions of U-Boot can be built for the 8X, the dependencies with the
SCFW only make it possible to use the latest version of U-Boot to avoid
unexpected behaviour.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
With this change, the ccimx6sbc and ccimx6qpsbc default images will now use the
xwayland backend instead of x11.
https://jira.digi.com/browse/DEL-7221
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
Remove all v4.9 recipes and build Linux using the same branch on all platforms.
The .inc files were only needed because of the existence of multiple Linux
versions, but that's not the case anymore, so remove them.
https://jira.digi.com/browse/DEL-7221
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The cryptoauthlib package is being added in digi-defaults.inc, which is parsed
before this file. Setting the variable here overwrites its previous value,
causing the cryptoauthlib package to be left out of the rootfs. Append to the
variable instead of overwriting it to avoid this.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Aside from adding the wireless-regdb-static support, this NXP package needs to
be included in the rootfs so the regulatory fw gets loaded in userspace.
https://jira.digi.com/browse/DEL-7133
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Disable all encryption support by default on CC8X and CC8MN platforms so
the default built images can be directly built.
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
This update is a cosmetic one and removes the RAM frequency from the SCFW
filenames. Reflect this change in the RAM_CONFIGS variable and in the uSD/UUU
installation scripts.
As a result, the imx-boot filenames will no longer have the RAM frequency
either.
https://jira.digi.com/browse/DEL-7096
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Modify the imx-seco recipe so it deploys the B0 and C0 versions of the SECO
firmware, Then, modify the imx-boot recipe so it builds every possible
combination of:
* RAM configuration
* imx-boot target (with and without M4 demos)
* Silicon revision
https://jira.digi.com/browse/DEL-7069
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@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>
The variable BT_DEVICE_NAME is used to name the Bluetooth device name on
the BlueZ configuration file. Re-use the contents of DIGI_FAMILY (except
for ccimx6qp which re-writes it) to simplify platform definitions.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
- WLAN_P2P_INTERFACE is the same for all platforms: "p2p0".
- WLAN_P2P_DEVICE_NAME can be built out of ${DIGI_FAMILY} except for
the ccimx6qp, that's why it has a weak default assignment.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
Default version is defined in poky layer, this commit also modifies
the preferred version to match with the new one.
https://jira.digi.com/browse/DEL-7013
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Remove support to kernel v4.14 and move platforms to use the new
kernel v5.4
https://jira.digi.com/browse/DEL-7013
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Add Trustfence support for signing imx-boot images:
- Install a different U-Boot signing script for images with U-Boot SPL.
- Store mkimage log for later use in the signing script
- make 'print_hab_log' and store its log for later use in the signing script
https://jira.digi.com/browse/DEL-7023
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@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>
Update the values of the MACHINE_SOCARCH_FILTER variable with the ones in
meta-fsl-bsp-release's imx-base.inc.
https://jira.digi.com/browse/DEL-6932
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
For the i.MX8M processors, the do_deploy support is provided by
the upstream recipe firmware-imx-8m.
https://jira.digi.com/browse/DEL-6911
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 meta-freescale-3rdparty layer used for the mainline bsp support does
not support the WiFi interface on thud. WiFi is currently merged on master
so it will probably be available on Zeus (2.8).
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
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>
Similar to the way the u-boot recipe does, create a symlink to the default
bootable artifact.
Since they are overwritten on every loop, this requires that the default
RAM configuration is set the last on the list of RAM_CONFIGS (same
convention than the one used on UBOOT_CONFIGS).
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6641
Even though our ccimx6 and ccimx6qp images were using Linux v4.9 sources
correctly, they were using the same recipe as our images with Linux v4.14.
Technically, both recipes are identical (save for the branch name), but each
Linux version should have its own recipe.
Also, make sure that ccimx6/ccimx6qp images are built with our version of the
linux-imx-headers recipe instead of the one in meta-freescale.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Removing the flag breaks the build of the freetype package and possibly others.
Leave the flag as it is for now.
This reverts commit e4cbeafa1c.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This option configures gcc to use PIE by default, which is good from a security
standpoint. However, the files necessary to compile applications statically
with PIE support are missing from glibc, causing builds to fail. Said files
were removed on purpose in poky commit 472c86127ab57759588e5ec53c75ebb52667f094
because static PIE binaries apparently don't work very well when using gcc 7.x.
Instead of enabling static PIE support for glibc and risking runtime failures,
revert to our old situation and remove default PIE suport for gcc.
https://jira.digi.com/browse/DEL-6558
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
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
Remove the linux-v4.20 recipe and use the linux-fslc kernel recipe in
meta-freescale-3rdparty instead.
Signed-off-by: Alex Gonzalez <alex.gonzalez@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>
This adds support for U-Boot v2018.03 for CC8X platforms only.
Create 'digi-u-boot.inc' with the common definitions for both v2017.03
and v2018.03.
https://jira.digi.com/browse/DUB-881
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@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)
In Yocto 2.6, this variable is null whenever systemd is enabled. Explicitly set
this variable to keep some necessary scripts in /etc/init.d.
https://jira.digi.com/browse/DEL-6415
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Also, remove sysvinit and add pam, which is needed by weston+systemd.
https://jira.digi.com/browse/DEL-6415
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
cryptoauth-openssl-engine is not compatible with OpenSSL v1.1.x, until
it will be supported, we disable it.
https://jira.digi.com/browse/DEL-6412
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The SDMA firmware does no longer live inside the kernel tree.
It must now be installed on the rootfs.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-6420
Just add the following to the conf/local.conf file:
MACHINEOVERRIDES .= ":use-mainline-bsp"
The defconfig is the mainline imx_v6_v7_defconfig.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Since we were modifying UBOOT_SYMLINK for the ccimx8x, we were generating
u-boot symlinks with imx-boot names. This also caused the imx-boot recipe to
fail during compilation, because it couldn't find the old UBOOT_SYMLINK that
we replaced.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Some overrides that were missing (imxgpu, imxdpublit) are needed for certain
packages to build.
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 package includes applications to:
- Update the MCA firmware
- Manage different MCA settings
- Configure the tamper settings
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
This package is the combination of U-Boot and the other i.MX firmware binaries.
In our case, these binaries are: the SCFW, the ATF and the DCD.
The recipe has been ported from the meta-fsl-bsp-release repo, with a couple of
important changes:
* Support for our platform (based on the mx8qxpa0, which uses A0-specific
parameters for mkimage and appends the DCD explicitly)
* Support for multiple UBOOT_CONFIG values (NXP only uses one UBOOT_CONFIG
string per platform; so the compile, install and deploy functions had to
be tweaked to build both 1GB and 2GB variants for our platform).
Our DCD patch used in imx-mkimage is also used, since both packages share the
same repo and imx-boot is the one responsible for generating the final,
bootable image.
https://jira.digi.com/browse/DEL-6085
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
U-Boot's 'dboot' command now supports uncompressing Image.gz.
This will be the default kernel image type for the CC8X.
This also changes the names of the device tree artifacts, that must be
updated on the boot script. While on it, add support for all the SOM
variants (wireless and non-wireless).
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
- This is an AARCH64 platform that requires to build "Image", so let's
change KERNEL_IMAGETYPE to a weak assignment in imx-digi-base.inc
- The device tree is inside a vendor folder.
- For the moment, this platform builds from a different branch.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-5936
With this patch a user can provide his own kernel 'defconfig' file by:
- setting the variable KERNEL_DEFCONFIG to a custom kernel configuration
file inside the kernel repository.
- setting the variable KERNEL_DEFCONFIG to a kernel configuration file
using the full path to the file.
- clearing the variable KERNEL_DEFCONFIG and providing a kernel
configuration file in the layer (in this case the file must be named
'defconfig').
Otherwise the default platform's kernel configuration file will be taken
directly from the Linux source code tree.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
This adds support for U-Boot v2017.03 for all platforms (including CC8X).
For legacy v2015.04:
- Renames u-boot.inc as a versioned file only for v2015.04.
- Moves boot/install scripts from versioned folder into non-versioned
folder (since the scripts remain the same between versions).
For new v2017.03:
- Re-uses poky's u-boot.inc in rocko for v2017.03
- DEY recipe re-writes the do_compile for special U-Boot configuration
required for TrustFence.
- DEY recipe appends the do_deploy, for U-Boot scripts and deploy of
special TrustFence artifacts.
- Adds u-boot-dtb.xxx to UBOOT_CONFIG, required for new U-Boots.
- Adds CC8X scripts.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-5936
Add initial support for Digi ConnectCore 8X SBC Express.
- ccimx6qp was used as reference machine from meta-digi.
- imx8qxpmek was used as a reference machine from meta-fsl-bsp-release.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-5936
As a side effect, remove U-Boot entry point variable and LOADADDR
extra parameter from the kernel recipe.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-5554
U-Boot has been able to boot kernel zImage for a long time so make this
the default kernel image.
For the CC6 we still want to use uImage for compatibility reasons.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-5237
Add initial support for Digi's ConnectCore 6 QuadPlus SBC.
The ccimx6qp platform has the QCA6564 chip instead of the
other Atheros chips and included the Atmel ECC508A cryptographic
chip.
https://jira.digi.com/browse/DEL-5082
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The current value only allows partitions of up to 8 MiB, which is not
enough for the 0x04 variant (which uses a linux partition of 24 MiB by
default).
This new value allows for up to 32 MiB (assuming 128 KiB erase block size).
Also add comments explaining the -c value and maximum partition sizes
supported.
https://jira.digi.com/browse/DEL-4971
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
After the 'ccardimx28js' platform removal, these variables and machine
features are not used anymore, so remove them.
https://jira.digi.com/browse/DEL-4771
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This is required to be able to use the whole RootFS partition which is
512 MiB in the 0x04 CC6UL SOM variant.
The old value only allowed to manage partitions of up to 256 MiB, this new
value allows for up to 1 GiB (assuming 128 KiB erase block size).
https://jira.digi.com/browse/DEL-4567
Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com>
This library adds support to use the Atmel CryptoAuth device available
in the ConnectCore 6UL.
https://jira.digi.com/browse/DEL-4284
Signed-off-by: Diaz de Grenu, Jose <Jose.DiazdeGrenu@digi.com>
The main purpose is to improve our kits usability. This way users do not need
to follow the steps in the documentation to change from static to DHCP IPs.
https://jira.digi.com/browse/DEL-3821
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
This commit adds the wireless concurrent mode as a default
configuration to the CC6UL machine.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-3818
This commit adds a wpa supplicant P2P configuration file and configures
the p2p0 interface automatically at pre-up.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The i.MX6UL supports some basic multimedia functionality
using the pixel pipeline (PXP).
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-2358
This application can be used to:
- Update the MCA firmware
- Configure the tamper settings
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-3230
This commit adds the proper DEFAULTTUNE and overrides for the ccimx6ul
family of modules.
https://jira.digi.com/browse/DEL-3102
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The name "ext-eth" seems to indicate "External Ethernet". Rename that variable
and related ones to a more proper name like second ethernet.
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
This reverts commit b8f50680e5.
The support to read and write to an encrypted environment has been added, so
there is no need to exclude the u-boot-fw-utils anymore.
https://jira.digi.com/browse/DEL-2836
Signed-off-by: Diaz de Grenu, Jose <Jose.DiazdeGrenu@digi.com>
APM is an ancient power management API mainly for x86. There is an
optional emulation layer for ARM, but none of our platforms is using
it, so just remove the machine feature.
https://jira.digi.com/browse/DEL-2745
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
enabled
There is currently no support on fw_printenv/fw_setenv to access an
encrypted environment.
This commit removes the package if U-Boot environment encryption is
enabled to avoid environment corruption on access.
It also documents the issue as a known issue.
https://jira.digi.com/browse/DEL-2625
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
U-Boot environment on the CC6UL NAND is located at partition /dev/mtd1:
- original copy is located at offset 0 in the partition
- redundant copy is located 1 erase block (128K) after the original copy
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-2552
The size of the destination partition (linux) is around 14MiB so the
max-leb-cnt must be reduced compared to the one used for the rootfs
partition.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-2697
This commit will add the cryptodev module to the CC6UL kernel to use
the CAAM from user space through this device.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-2719
This function is deprecated in favor of bb.utils.contains. The same
change has been done in other layers.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This daemon (rngd) feeds random data from hardware device to kernel
entropy pool.
https://jira.digi.com/browse/DEL-2501
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This module is the interface between user-space (openssl, gnutls) and
the hardware cryptographic acceleration support (CAAM).
This commit installs the module in the rootfs and configures it so it is
loaded on boot.
https://jira.digi.com/browse/DEL-2501
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Arturo Buzarra
Javier Viguera
Mike Engel
Isaac Hermida
Gabriel Valcazar
Hector Palacios
Gonzalo Ruiz
Alex Gonzalez
Jose Diaz de Grenu
Tatiana Leon