meta-openembedded/meta-oe
Miaoqing Pan e44b0f2575
hostapd: enable 802.11be, SAE-PK, OWE, SuiteB, ACS, and MBO support
hostapd has supported IEEE 802.11be (Wi-Fi 7) for over three years. Given
the growing market demand for Wi-Fi 7, it is now an appropriate time to
enable support for IEEE 802.11be Extremely High Throughput (EHT). Note
that CONFIG_IEEE80211AX is a mandatory prerequisite for setting
CONFIG_IEEE80211BE.

This patch also enables the following build-time options in defconfig,
all of which have no runtime impact:
SAE Public Key (SAE_PK)
Opportunistic Wireless Encryption (OWE)
Suite B and Suite B 192
Automatic Channel Selection (ACS)
Multiband Operation (MBO)

Signed-off-by: Miaoqing Pan <miaoqing.pan@oss.qualcomm.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-07-17 08:53:08 -07:00
..
classes signing.bbclass: make PEM loading compatible with OpenSC 0.26.0 2025-07-02 09:48:26 -07:00
conf reproducibility: move known non-repro list to layer.conf 2025-06-20 10:34:11 -07:00
dynamic-layers bpftrace: Remove absolute buildtime paths in cmake files 2025-07-16 23:12:37 -07:00
files static-passwd-meta-oe: add flatpak user 2025-04-19 14:36:07 -07:00
lib/oeqa/selftest/cases
licenses licenses/X11: remove license 2025-04-29 08:45:35 -07:00
recipes-benchmark meta-openembedded/all: adapt to UNPACKDIR changes 2025-06-25 06:44:52 -07:00
recipes-bsp fwupd: set vendor_ids_dir 2025-07-15 07:49:27 -07:00
recipes-connectivity hostapd: enable 802.11be, SAE-PK, OWE, SuiteB, ACS, and MBO support 2025-07-17 08:53:08 -07:00
recipes-core opencl-icd-loader: allow to build with cmake 4 2025-07-10 10:46:23 -07:00
recipes-crypto cryptsetup: upgrade 2.7.5 -> 2.8.0 2025-07-07 10:00:53 -07:00
recipes-dbs leveldb: Allow to build with CMake 4+ 2025-07-15 07:49:27 -07:00
recipes-devtools uftrace: Fix build failure on x86 2025-07-16 15:42:59 -07:00
recipes-extended wxwidgets: add back SRCREV 2025-07-16 22:24:55 -07:00
recipes-gnome meta-openembedded/all: adapt to UNPACKDIR changes 2025-06-25 06:44:52 -07:00
recipes-graphics libsdl3: upgrade 3.2.16 -> 3.2.18 2025-07-15 23:54:14 -07:00
recipes-kernel kernel-selftest: Fix PTP selftest compilation for kernel 6.7+ 2025-07-09 09:16:08 -07:00
recipes-multimedia wavpack: Upgrade 5.6.0 -> 5.8.1 to allow CMake 4+ compatibility 2025-07-09 09:16:06 -07:00
recipes-navigation proj: Upgrade to 9.6.2 release 2025-07-12 13:50:02 -07:00
recipes-networking/cyrus-sasl meta-openembedded/all: adapt to UNPACKDIR changes 2025-06-25 06:44:52 -07:00
recipes-printing gutenprint: fix a build race-condition 2025-07-04 09:42:10 -07:00
recipes-security meta-openembedded/all: adapt to UNPACKDIR changes 2025-06-25 06:44:52 -07:00
recipes-shells meta-openembedded/all: adapt to UNPACKDIR changes 2025-06-25 06:44:52 -07:00
recipes-support freerdp: Allow to build with CMake 4+ 2025-07-15 00:25:29 -07:00
recipes-test linux-serial-test: Bump SRCREV to allow CMake 4+ compatibility 2025-07-11 08:35:27 -07:00
COPYING.MIT
README.md
SECURITY.md

meta-oe

This layer depends on:

URI: git://github.com/openembedded/openembedded-core.git branch: master

luajit recipe requires host compiler to be able to generate 32bit code when target is 32bit e.g. arm, so ensure that $CC -m32 is functional on build host, if building this recipe, needed packages to fullfit this might have different names on different host distributions e.g. on archlinux based distributions install prerequisites like below

pacman -S lib32-gcc-libs lib32-glibc

Ubuntu sudo apt-get install gcc-multilib linux-libc-dev:i386

Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject'

When sending single patches, please use something like: 'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix="meta-oe][PATCH"'

You are encouraged to fork the mirror on GitHub https://github.com/openembedded/meta-openembedded to share your patches, this is preferred for patch sets consisting of more than one patch.

Note, it is discouraged to send patches via GitHub pull request system. Such patches get less attention from developers and can be mishandled or not reviewed properly. Please use emails instead. For exemple, you can use 'git request-pull' to generate an email referencing your git repository.

Other services like GitLab, repo.or.cz or self-hosted setups are of course accepted as well, 'git fetch ' works the same on all of them. We recommend GitHub because it is free, easy to use, has been proven to be reliable and has a really good web GUI.

layer maintainer: Khem Raj raj.khem@gmail.com