On Thu, 4 Dec 2025 at 16:49, Jouni Malinen <[email protected]> wrote: > > On Thu, Dec 04, 2025 at 03:56:06PM +0800, Miaoqing Pan wrote: > > Jouni, do you think it’s the right time to enable CONFIG_IEEE80211BE and > > CONFIG_OWE in the upstream codebase? > > defconfig in upstream is mainly a documentation of the .config file. It > is not a specific recommendation of how to configure any particular > build. Each project should consider what are appropriate features for > their use cases instead of doing this based on what happens to be > enabled in the defconfig file. In other words, I would store build > configuration in some other location that is specific to a platform or > project using wpa_supplicant.
The specific patches that are being proposed for defconfig are these: https://patchwork.yoctoproject.org/project/oe-core/patch/[email protected]/ https://patchwork.yoctoproject.org/project/oe-core/patch/[email protected]/ Is it ok to apply them upstream? They seem like commonly wanted default features, as of late 2025 (because they're suggested by Qualcomm as defaults for the yocto project). I also think upstream defconfig should suggest sensible defaults, and also not claim something is 'draft' or 'experimental' when it no longer is. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#227299): https://lists.openembedded.org/g/openembedded-core/message/227299 Mute This Topic: https://lists.openembedded.org/mt/116508467/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
