src/sys/dev/ath, branch mainFreeBSD source treehttps://cgit-dev.freebsd.org/src/atom?h=main2026-05-15T21:59:07Znet80211: define a type for rssi values2026-05-15T21:59:07ZBjoern A. Zeebbz@FreeBSD.org2025-06-19T00:05:27Zurn:sha1:96eaa6857ffe009c141c5a6dbea88f96efed9b2d
Due to net80211 keeping values in 0.5dBm relative to the noise floor
an int8_t is not good enough to prevent a double wrap around, which
means the reported rssi values can be wrong (see D50928 or likely
a commit in the future for more information).
In order to address the problem and not break the userspace API,
start by defining a type within the kernel and use that. In a
next step we will then update the int8_t to int16_t to avoid the
problem up to the ioctl code. This will then allow us to work
on the the user space API indepedently (see PR 293016 for possible
impact outside the base system).
No functional changes intended.
Sponsored by: The FreeBSD Foundation
MFC after: 3 days
Reviewed by: adrian
Differential Revision: https://reviews.freebsd.org/D57021
ath: migrate to new net80211 encryption key API2026-02-26T03:49:27ZAdrian Chaddadrian@FreeBSD.org2026-02-26T03:49:27Zurn:sha1:a54a36c40f07092ace706ccec8c3db6f6a1877c1
Migrate to the new encryption key API rather than poking at the
key struct directly.
Differential Revision: https://reviews.freebsd.org/D54479
ath_hal(4): Fix a typo in a source code comment2026-01-31T15:20:32ZGordon Berglinggbe@FreeBSD.org2026-01-31T15:20:32Zurn:sha1:a17659fe260ce16c1e373b543ca9f13cc14340ea
- s/arithmatic/arithmetic/
MFC after: 5 days
ath(4): Fix a typo in a device messsage2025-10-31T18:50:40ZGordon Berglinggbe@FreeBSD.org2025-10-29T15:26:59Zurn:sha1:3eaa2a852b475c7f063bbf677fa536e76514d309
- s/Orignal/Original/
MFC after: 5 days
ath: fix ath_buf leak if ath_tx_tag_crypto() returns an error2025-10-01T02:21:01ZAdrian Chaddadrian@FreeBSD.org2025-10-01T02:21:01Zurn:sha1:f7aad20db59210a4411559d07976a48809b3b0a7
If ath_tx_tag_crypto() returns an error, then ath_tx_normal_setup()
should consume the mbuf and return an error, so the caller knows to
free the ath_buf. But it wasn't.
This fixes issues I've seen locally where a an AP VAP constantly hits
error conditions (due to other RF/PHY/MAC chipset issues which I haven't
yet figured out) and encryption fails because the station goes away
whilst something's being queued.
Locally tested:
* AR9380, AP mode (2G HT20, 5G HT20, 5G HT40)
net80211: convert the rest of the native net80211 drivers to SEQNO_OFFLOAD2025-09-20T00:42:45ZAdrian Chaddadrian@FreeBSD.org2025-06-10T04:22:10Zurn:sha1:785edcc2af5ae32c24f5caf5b9552f62bdae33ee
* Convert the rest of the drivers to implement driver/offloaded sequence
number handling.
* For drivers that implement their own sequence number space handling
for A-MPDU, only call ieee80211_output_seqno_assign() if the frame
isn't tagged with M_AMPDU_MPDU, which mirrors the original net80211
sequence number behaviour. (Except of course, the assignment is
now happening during final encap/transmit, not early in encap.)
Locally tested (sta mode):
* ath
* iwn
* bwi
* bwn
* iwm
* otus
* ral
Differential Revision: https://reviews.freebsd.org/D50772
Okayed by: bz
net80211 / LinuxKPI: 802.11: revert / redo enum ieee80211_sta_rx_bw2025-08-30T07:38:22ZBjoern A. Zeebbz@FreeBSD.org2025-08-14T01:28:29Zurn:sha1:06527b2818f2748fa6eedc2fd418379ef7f99bd9
The initial thought of migrating the LinuxKPI 802.11 enum into net80211
for shared use did not work out well. Currently in the need for yet
another adjustment, I decided to undo/de-couple net80211 and
LinuxKPI 802.11 again.
The enum name now gets used in LinuxKPI based wifi drivers and it
turns out it is spelt differntly than what I used initially.
This creates a conflict.
net80211 still in the need to be able to express BW_320 in an uint8_t
will likely be fine with the current solution as well. Rename the
enum and prefixes in net80211 to "net80211" instead of "ieee80211".
Apart from the names/prefix we leave the values the same.
In LinuxKPI add the enum with the expected name and use it there
throughout to make modern versions of LinuxKPI based wifi drivers
compile.
Sponsored by: The FreeBSD Foundation
Fixes: ca389486a9599, 2c8b0d6205f6f
MFC after: 3 days
Reviewed by: adrian
Differential Revision: https://reviews.freebsd.org/D52064
machine/stdarg.h -> sys/stdarg.h2025-06-11T16:39:02ZBrooks Davisbrooks@FreeBSD.org2025-06-11T16:39:02Zurn:sha1:e453e498cbb88570a3ff7b3679de65c88707da95
Switch to using sys/stdarg.h for va_list type and va_* builtins.
Make an attempt to insert the include in a sensible place. Where
style(9) was followed this is easy, where it was ignored, aim for the
first block of sys/*.h headers and don't get too fussy or try to fix
other style bugs.
Reviewed by: imp
Exp-run by: antoine (PR 286274)
Pull Request: https://github.com/freebsd/freebsd-src/pull/1595
ath(4): Fix a typo in a source code comment2025-04-28T09:22:10ZGordon Berglinggbe@FreeBSD.org2025-04-28T09:22:10Zurn:sha1:3ad86f460fa81ecc036fb5af25848f10b68b4019
- s/chang/change/
MFC after: 3 days
ath_rate_sample: fix setting HT rates2025-03-01T23:32:56ZAdrian Chaddadrian@FreeBSD.org2025-03-01T22:38:53Zurn:sha1:10c633ab1204e13d6fbad9f0f474229eed5fd280
ieee80211_node_set_txrate_ht_mcsrate() takes an MCS rate from 0..76,
the high bit (IEEE80211_RATE_MCS) must not be set.
This is definitely my fault - I likely didn't get to testing this
diff when I changed it from ieee80211_node_set_txrate_dot11rate()
just before landing.
Differential Revision: https://reviews.freebsd.org/D49197
Reviewed by: bz