From: "Tom Hochstein" <tom.hochstein@nxp.com>
To: openembedded-core@lists.openembedded.org
Cc: otavio@ossystems.com.br, Tom Hochstein <tom.hochstein@nxp.com>
Subject: [PATCH] [RFC] openssl: Enable cryptodev-linux by default
Date: Thu, 28 Jan 2021 15:35:04 -0600 [thread overview]
Message-ID: <20210128213504.3821-1-tom.hochstein@nxp.com> (raw)
This is a Request for Comment. Would it be a good idea to enable cryptodev-linux
by default, gaining hardware acceleration where supported? Are there any
unacceptable drawbacks? What happens on hardware without acceleration?
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
---
meta/recipes-connectivity/openssl/openssl_1.1.1i.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-connectivity/openssl/openssl_1.1.1i.bb b/meta/recipes-connectivity/openssl/openssl_1.1.1i.bb
index 5617f337e0..d4c19f1a52 100644
--- a/meta/recipes-connectivity/openssl/openssl_1.1.1i.bb
+++ b/meta/recipes-connectivity/openssl/openssl_1.1.1i.bb
@@ -28,7 +28,7 @@ SRC_URI[sha256sum] = "e8be6a35fe41d10603c3cc635e93289ed00bf34b79671a3a4de64fcee0
inherit lib_package multilib_header multilib_script ptest
MULTILIB_SCRIPTS = "${PN}-bin:${bindir}/c_rehash"
-PACKAGECONFIG ?= ""
+PACKAGECONFIG ?= "cryptodev-linux"
PACKAGECONFIG_class-native = ""
PACKAGECONFIG_class-nativesdk = ""
--
2.17.1
next reply other threads:[~2021-01-28 21:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 21:35 Tom Hochstein [this message]
2021-01-28 21:40 ` [OE-core] [PATCH] [RFC] openssl: Enable cryptodev-linux by default Otavio Salvador
2021-01-29 1:15 ` Khem Raj
2021-01-29 8:32 ` Diego Santa Cruz
2021-01-29 20:39 ` Andre McCurdy
2021-01-29 20:45 ` Otavio Salvador
2021-01-29 21:14 ` Andre McCurdy
2021-01-29 21:20 ` Otavio Salvador
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210128213504.3821-1-tom.hochstein@nxp.com \
--to=tom.hochstein@nxp.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox