The firmware 3.16.1 has been released the 2023-05-02.
Here the last modifications (only modifications tagged [LMAC] have an
impact on Linux):
* [1670] - [LMAC] Fixed support for WDS 4 address frames
* [1813] - [LMAC] Fixed an error that was causing the scan complete
indication to be blocked
* [1832] - [UMAC] Fixed an issue blocking connection to specific Asus
routers
* [1820] - [UMAC] Added a new API to obtain Wi-Fi diagnostics
information
* [1825] - [UMAC] The TX rate mask can be applied in AP mode
* [1822] - [UMAC] Fixed an error that was causing access point packets
to be encrypted multiple times
* [1800] - [UMAC] Add an API to forward probe request when running in
AP mode
Signed-off-by: Jérôme Pouiller <jerome.pouiller@silabs.com>
Signed-off-by: Josh Boyer <jwboyer@kernel.org>
The firmware 3.14 has been released the 2022-01-26.
Here the last modifications (only modifications tagged [LMAC] have an
impact on Linux):
* [1792] - [UMAC] Fix an issue causing the softAP mode to forward
unencrypted data frames
* [1794] - [UMAC] Fix a connection timeout while connecting to an AP
with a hidden SSID
* [1724] - [UMAC] Add an API to select the rate algorithm to use
* [1757] - [UMAC] Handle invalid size parameters in
sl_wfx_send_scan_command()
* [1767] - [LMAC] Prevent defragmentation from accepting mixed
encrypted/plaintext fragments
* [1768] - [LMAC] Prevent defragmentation from accepting
non-consecutive packet numbers for fragments
* [1769] - [LMAC] Prevent defragmentation from accepting fragments
encrypted with different keys
* [1770] - [LMAC] Clear defragmentation cache upon reconnection
* [1731] - [LMAC] Fix an issue in concurrent mode where packets were
passed to the wrong interface
* [1745] - [LMAC] Fix an issue with specific information elements
handling leading to a firmware exception
* [1751] - [UMAC] Configured CCA mode is not overwritten anymore
when starting an interface
Signed-off-by: Jérôme Pouiller <jerome.pouiller@silabs.com>
Signed-off-by: Josh Boyer <jwboyer@kernel.org>
WiFi device maintainer expressed he prefers to use the same name for the
driver and the firmware directory[1].
Since the driver is not yet merged, the renaming does not break
anything.
[1]: https://lore.kernel.org/netdev/87sfxlj6s1.fsf@codeaurora.org/
Signed-off-by: Jérôme Pouiller <jerome.pouiller@silabs.com>
Signed-off-by: Josh Boyer <jwboyer@kernel.org>
Jérôme Pouiller