From: Peter Seiderer <ps.report@gmx.net>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Matt Weber <matthew.weber@collins.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/iwd: enable required kernel dependencies
Date: Wed, 1 Dec 2021 18:34:13 +0100 [thread overview]
Message-ID: <20211201183413.2a98291c@gmx.net> (raw)
In-Reply-To: <20211201135103.2302297-1-james.hilliard1@gmail.com>
Hello James,
On Wed, 1 Dec 2021 06:51:03 -0700, James Hilliard <james.hilliard1@gmail.com> wrote:
> Required kernel options are listed in check_crypto() in srv/main.c:
> https://git.kernel.org/pub/scm/network/wireless/iwd.git/tree/src/main.c?h=1.20#n268
Thanks for doing this (one less point on my long standing ToDo list) ;-)
>
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> ---
> package/iwd/iwd.mk | 30 ++++++++++++++++++++++++++++++
> 1 file changed, 30 insertions(+)
>
> diff --git a/package/iwd/iwd.mk b/package/iwd/iwd.mk
> index 96bdc56e93..8bcd406ea0 100644
> --- a/package/iwd/iwd.mk
> +++ b/package/iwd/iwd.mk
> @@ -63,4 +63,34 @@ define IWD_INSTALL_INIT_SYSV
> ln -sf /tmp/iwd/hotspot $(TARGET_DIR)/var/lib/iwd/hotspot
> endef
>
> +define IWD_LINUX_CONFIG_FIXUPS
> + $(call KCONFIG_ENABLE_OPT,CONFIG_ASYMMETRIC_KEY_TYPE)
> + $(call KCONFIG_ENABLE_OPT,CONFIG_ASYMMETRIC_PUBLIC_KEY_SUBTYPE)
> + $(call KCONFIG_ENABLE_OPT,CONFIG_CRYPTO_AES)
> + $(call KCONFIG_ENABLE_OPT,CONFIG_CRYPTO_AES_NI_INTEL)
> + $(call KCONFIG_ENABLE_OPT,CONFIG_CRYPTO_AES_X86_64)
Not sure if it is good idea to add the x86_64 specific ones unconditionally
(they are marked in check_crypto() with ADD_OPTIONAL instead of ADD_MISSING)?
Regards,
Peter
> + $(call KCONFIG_ENABLE_OPT,CONFIG_CRYPTO_CBC)
> + $(call KCONFIG_ENABLE_OPT,CONFIG_CRYPTO_CMAC)
> + $(call KCONFIG_ENABLE_OPT,CONFIG_CRYPTO_DES)
> + $(call KCONFIG_ENABLE_OPT,CONFIG_CRYPTO_DES3_EDE_X86_64)
> + $(call KCONFIG_ENABLE_OPT,CONFIG_CRYPTO_ECB)
> + $(call KCONFIG_ENABLE_OPT,CONFIG_CRYPTO_HMAC)
> + $(call KCONFIG_ENABLE_OPT,CONFIG_CRYPTO_MD4)
> + $(call KCONFIG_ENABLE_OPT,CONFIG_CRYPTO_MD5)
> + $(call KCONFIG_ENABLE_OPT,CONFIG_CRYPTO_SHA1)
> + $(call KCONFIG_ENABLE_OPT,CONFIG_CRYPTO_SHA1_SSSE3)
> + $(call KCONFIG_ENABLE_OPT,CONFIG_CRYPTO_SHA256)
> + $(call KCONFIG_ENABLE_OPT,CONFIG_CRYPTO_SHA256)
> + $(call KCONFIG_ENABLE_OPT,CONFIG_CRYPTO_SHA256_SSSE3)
> + $(call KCONFIG_ENABLE_OPT,CONFIG_CRYPTO_SHA512)
> + $(call KCONFIG_ENABLE_OPT,CONFIG_CRYPTO_SHA512_SSSE3)
> + $(call KCONFIG_ENABLE_OPT,CONFIG_CRYPTO_USER_API_HASH)
> + $(call KCONFIG_ENABLE_OPT,CONFIG_CRYPTO_USER_API_SKCIPHER)
> + $(call KCONFIG_ENABLE_OPT,CONFIG_KEYS)
> + $(call KCONFIG_ENABLE_OPT,CONFIG_KEY_DH_OPERATIONS)
> + $(call KCONFIG_ENABLE_OPT,CONFIG_PKCS7_MESSAGE_PARSER)
> + $(call KCONFIG_ENABLE_OPT,CONFIG_PKCS8_PRIVATE_KEY_PARSER)
> + $(call KCONFIG_ENABLE_OPT,CONFIG_X509_CERTIFICATE_PARSER)
> +endef
> +
> $(eval $(autotools-package))
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-12-01 17:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 13:51 [Buildroot] [PATCH 1/1] package/iwd: enable required kernel dependencies James Hilliard
2021-12-01 17:34 ` Peter Seiderer [this message]
2021-12-01 23:15 ` James Hilliard
2021-12-04 20:28 ` Thomas Petazzoni
2021-12-04 23:43 ` James Hilliard
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=20211201183413.2a98291c@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=matthew.weber@collins.com \
/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