Commit Graph

8 Commits

Author SHA1 Message Date
Javier Viguera 373f061650 dey: cosmetic, mark patches as DEY specific
Our distribution is Digi Embedded Yocto (DEY), so use that to mark the
upstream status of the patches in our layer.

Signed-off-by: Javier Viguera <javier.viguera@digi.com>
2024-10-22 15:48:00 +02:00
Gabriel Valcazar 2bc985cbea global: add Upstream-Status tag to all patches
This avoids a QA error that is triggered if a patch is missing said tag

https://onedigi.atlassian.net/browse/DEL-9011

Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
2024-10-17 13:03:37 +02:00
Isaac Hermida 0c642ed7ec Update Digi Copyright header
Standarize the Copyright header according to company policy.

Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
2024-07-15 09:28:58 +02:00
Javier Viguera adbb511484 meta-digi: remove True option to getVar
True is the default since long time ago, and thus not necessary. This
follows similar changes done in other layers.

Command used:

sed -e 's|\(d\.getVar \?\)( \?\([^,()]*\), \?True)|\1(\2)|g' -i $(git grep -E 'getVar ?\( ?([^,()]*), ?True\)' | cut -d':' -f1 | sort -u)

Signed-off-by: Javier Viguera <javier.viguera@digi.com>
2023-02-24 16:24:47 +01:00
Javier Viguera b2bc9539b7 wolfssl: add basic instructions to use FIPS-validated version
https://onedigi.atlassian.net/browse/DEL-8036

Signed-off-by: Javier Viguera <javier.viguera@digi.com>
2022-09-02 11:21:44 +02:00
Javier Viguera 52bececebc wolfcrypttest: fix for FIPS enabled wolfSSL library
FIPS does not support MD5

https://onedigi.atlassian.net/browse/DEL-8036

Signed-off-by: Javier Viguera <javier.viguera@digi.com>
2022-09-01 19:12:17 +02:00
Javier Viguera df327f8757 wolfcrypttest: define "long" and "long long" type size
To prevent runtime error:

Sizeof mismatch (build) 0 != (run) 2
Build vs runtime math mismatch
 error = -1000

https://onedigi.atlassian.net/browse/DEL-8036

Signed-off-by: Javier Viguera <javier.viguera@digi.com>
2022-08-31 17:30:36 +02:00
Javier Viguera b8e4507070 meta-digi-arm: add FIPS supported wolfssl recipe
We don't want the FIPS version of wolfssl to be used by default, so
the recipe is configured as:

DEFAULT_PREFERENCE = "-1"

Unfortunately, DEFAULT_PREFERENCE has lower precedence than the layer
priority, so we need to put the recipe in a layer with priority less
or equal to the other layers having wolfssl recipes (meta-openembedded,
meta-wolfssl). This means in our case using 'meta-digi-arm' instead of
'meta-digi-dey', in which conceptually would fit better.

https://onedigi.atlassian.net/browse/DEL-8036

Signed-off-by: Javier Viguera <javier.viguera@digi.com>
2022-08-31 17:30:36 +02:00