From: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
To: Miaoqing Pan <miaoqing.pan@oss.qualcomm.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] wpa-supplicant: enable 802.11be, MBO, OWE, and SuiteB support
Date: Sun, 19 Oct 2025 01:34:09 +0300 [thread overview]
Message-ID: <aPQV4Qy78RWUnImJ@umbar.lan> (raw)
In-Reply-To: <20250718030452.3459203-1-miaoqing.pan@oss.qualcomm.com>
On Fri, Jul 18, 2025 at 11:04:52AM +0800, Miaoqing Pan wrote:
> wpa_supplicant has supported IEEE 802.11be (Wi-Fi 7) for over three
> years. With growing market demand for Wi-Fi 7, it is now an
> appropriate time to enable IEEE 802.11be Extremely High Throughput
> (EHT) support - mainly for AP mode.
>
> This patch also enables the following features in defconfig:
> Opportunistic Wireless Encryption (OWE)
> Suite B and Suite B 192
> Multi Band Operation (MBO)
>
> Signed-off-by: Miaoqing Pan <miaoqing.pan@oss.qualcomm.com>
> ---
> v2: update prefix and commit message.
> ---
> .../wpa-supplicant/wpa-supplicant_2.11.bb | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant_2.11.bb b/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant_2.11.bb
> index 6dc76494f7..440d3a5c94 100644
> --- a/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant_2.11.bb
> +++ b/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant_2.11.bb
> @@ -37,6 +37,12 @@ do_configure () {
> ${MAKE} -C wpa_supplicant clean
> sed -e '/^CONFIG_TLS=/d' <wpa_supplicant/defconfig >wpa_supplicant/.config
>
> + sed -i -e 's/^#\(CONFIG_IEEE80211BE=y\)/\1/' \
> + -e 's/^#\(CONFIG_MBO=y\)/\1/' \
> + -e 's/^#\(CONFIG_OWE=y\)/\1/' \
> + -e 's/^#\(CONFIG_SUITEB=y\)/\1/' \
> + -e 's/^#\(CONFIG_SUITEB192=y\)/\1/' wpa_supplicant/.config
I was pointed out to this patch. Is there any reason why you don't
extend the previous line, which also patches the .config file?
> +
> if ${@ bb.utils.contains('PACKAGECONFIG', 'openssl', 'true', 'false', d) }; then
> echo 'CONFIG_TLS=openssl' >>wpa_supplicant/.config
> elif ${@ bb.utils.contains('PACKAGECONFIG', 'gnutls', 'true', 'false', d) }; then
> --
> 2.34.1
>
>
--
With best wishes
Dmitry
next prev parent reply other threads:[~2025-10-18 22:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 3:04 [PATCH v2] wpa-supplicant: enable 802.11be, MBO, OWE, and SuiteB support Miaoqing Pan
2025-10-18 22:34 ` Dmitry Baryshkov [this message]
2025-10-22 1:45 ` Miaoqing Pan
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=aPQV4Qy78RWUnImJ@umbar.lan \
--to=dmitry.baryshkov@oss.qualcomm.com \
--cc=miaoqing.pan@oss.qualcomm.com \
--cc=openembedded-core@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.