Files
meta-openembedded/meta-oe
Markus Volk d1a2c6c529 iwd: update 2.0 -> 2.3
ver 2.3:
	Fix issue with length calculation for WMM IE.
	Fix issue with channel number allocation off-by-one.
	Fix issue with cached session when TLS phase2 fails.
	Add support for FastReauthentication setting for EAP-TLS.

ver 2.2:
	Fix issue with handling FT and multiple roaming scans.
	Fix issue with handling multiple wiphy registrations.
	Fix issue with with EAP-PEAP session resumption.
	Add support for using PTK rekeying in AP mode.
	Add support for setting country IE in AP mode.
	Add support for setting WMM parameter IE in AP mode.

ver 2.1:
	Fix issue with handling FT-over-DS action.
	Fix issue with handling scan and 6 GHz support check.
	Fix issue with handling when periodic scans get aborted.
	Add support for using 5 GHz frequencies in AP mode.

Signed-off-by: Markus Volk <f_l_k@t-online.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2023-02-07 20:56:08 -08:00
..
2023-01-16 10:32:40 -08:00
2023-02-03 07:47:10 -08:00
2023-01-17 01:05:52 -08:00
2022-12-03 08:11:30 -08:00

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.

Other services like GitLab, repo.or.cz or self-hosted setups are of course accepted as well,
'git fetch <remote>' 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>