git: 6c4064d4ed - main - Status/2026Q2: grammar fixes
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 17 Jul 2026 16:50:44 UTC
The branch main has been updated by maxim:
URL: https://cgit.FreeBSD.org/doc/commit/?id=6c4064d4ed7b1756bb893502f7871af698c9078a
commit 6c4064d4ed7b1756bb893502f7871af698c9078a
Author: Maxim Konovalov <maxim@FreeBSD.org>
AuthorDate: 2026-07-17 16:49:05 +0000
Commit: Maxim Konovalov <maxim@FreeBSD.org>
CommitDate: 2026-07-17 16:49:05 +0000
Status/2026Q2: grammar fixes
---
.../en/status/report-2026-04-2026-06/lkpi-wireless.adoc | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/website/content/en/status/report-2026-04-2026-06/lkpi-wireless.adoc b/website/content/en/status/report-2026-04-2026-06/lkpi-wireless.adoc
index 004d7cb7be..cf0ed0d17a 100644
--- a/website/content/en/status/report-2026-04-2026-06/lkpi-wireless.adoc
+++ b/website/content/en/status/report-2026-04-2026-06/lkpi-wireless.adoc
@@ -45,7 +45,7 @@ As underlying ground works for Realtek and Mediatek various LinuxKPI 802.11 impl
* TX hardware crypto: the mt7921 would happily work with software crypto but once hardware crypto offload was enabled we would only receive some packets but not TX any correct frames anymore.
It turned out that depending on key type the driver would user a different path to the keys and we would set both keys the same way, essentially overwriting the 1st with the 2nd.
Fixed the argument passed down on the set key call to avoid this problem.
- This may also help rtw8x where we had seen occassional problems related to MC packets but validation is still pending.
+ This may also help rtw8x where we had seen occasional problems related to MC packets but validation is still pending.
* rates: started to fill in and update most of the LinuxKPI 802.11 rate fields (but one which would only be needed for mt7615).
Part of this work was originally done for rtw8x end of last year with a lot of it supplemented for Mediatek.
* Fixed a compatibility ordering problem: it turned out that some of the order of events we had implemented did not fully match the expectations of some drivers.
@@ -54,14 +54,14 @@ As underlying ground works for Realtek and Mediatek various LinuxKPI 802.11 impl
==== LinuxKPI changes:
-In addition to the 802.11 parts in LinuxKPI, there is also general LinuxKPI infrastructure which needs adjutments.
+In addition to the 802.11 parts in LinuxKPI, there is also general LinuxKPI infrastructure which needs adjustments.
* PAGE_IS_LKPI_PAGE: this is a project to convert an early day shortcut that a Linux struct page is 1:1 mapped to a native vm_page into a proper Linux struct page with a vm_page backing.
This is mostly needed for some Mediatek mt76 drivers, but also drm-kmod can finally undo some FreeBSD specific hacks after this lands.
* LinuxKPI PCI detach (cleanup) functions: the Mediatek driver would cause a kernel panic on unload or shutdown.
It turned out that the various LinuxKPI PCI cleanup routines were not fully correct as a comment had already hinted for one part.
We fixed this and also cleaned up some of the file.
- At the time of writing the reviews are still pending but we hope to have at least the esential parts committed soon.
+ At the time of writing the reviews are still pending but we hope to have at least the essential parts committed soon.
* The LinuxKPI IDR code is used by some Mediatek mt76 drivers but is also shared with drm-kmod and a bunch of semi-native drivers.
Unfortunately the framework has known problems (as some history showed) and does not match current expectations anymore.
Rewriting this is somewhat tricky due to the larger impact but we hope have it ready in early 26Q3.
@@ -71,7 +71,7 @@ In addition to the 802.11 parts in LinuxKPI, there is also general LinuxKPI infr
After the updates to Linux v7.0 the problems we had with some chipsets not being able to associate increased.
Both man:rtw88[4] and man:rtw89[4] now show various issues.
-One additional problem was discovered in that the man:rtw88[4] driver for at least one chipset would go off for 6s seconds, essentialy letting authentication run into timeouts.
+One additional problem was discovered in that the man:rtw88[4] driver for at least one chipset would go off for 6s seconds, essentially letting authentication run into timeouts.
It is not understood yet under which circumstances this will not happen, as it clearly does not seem to be a problem under Linux.
Sadly it was not possible to debug this in time for 15.1-RELEASE.
We hope to look into this in early 26Q3 in order to evaluate if a EN code be issued before 15.0 becomes EOL and fix the regressions.
@@ -111,7 +111,7 @@ I am not sure this is a good sign or not.
We appreciate all the feedback and problem reports we get and if they come in on bugzilla we also try to categorize them into specific groups (see link).
Some may seem to fall through the cracks but we generally try not to let that happen.
-Sometimes larger works are planned dedicated to the area of your problem and so may not see immedaite help, sometimes other things may be ahead of the queue.
+Sometimes larger works are planned dedicated to the area of your problem and so may not see immediate help, sometimes other things may be ahead of the queue.
If the issues are properly documented it will be easier to get back to them at a later time.
If you have any issues with (LinuxKPI based) wireless please try to use the official channels: check open PRs, send a note to the wireless mailing list, if needed drop me a private email (e.g., if you have a core dump with possible private information), or open a new PR if the issue is not yet known (or seems to fall through the cracks as then it is up for public tracking).