Add tx_ampdu_enable for run (function returns 0 for now meaning that no tx ampdu support in driver). Disable MCS32 RX/TX bits.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jun 2 2020
May 29 2020
May 28 2020
Add MCS table from datasheet. RX AMPDU works now (verified with a wireshark monitor).
May 27 2020
AMPDU advertisement
Enable AMPDU and set rxmax and density (hard coded values rn)
Use ieee80211 flags when setting htcaps
May 26 2020
Add mbuf tagging in rx path
Add MCS rates to run's rate table, print out tx descriptor and decide which PHY to use based on the rate / ridx instead of channel being HT20.
May 25 2020
May 24 2020
First 802.11n frames on the wire.
MCS Index is still 0, and its unclear why the run driver wants to operate at lower rates even when the device seems more capable.
Get 802.11n frames on the wire.
The MCS Index in the transmission is still 0 for everything we send out, that should be improved. Other bits in the txwi could be tweaker similar to rt2x00 but perhaps right now is a good time to look at the rx path to "learn" from incoming packets and operate at a higher rate. Not exactly clear why run operates at a low rate index.
May 22 2020
In D22840#549376, @adrian wrote:Why are the net80211 changes required? What's going on?
Exactly produce probe requests as rt2x00.
All the A-MPDU and RX MCS bitsets are now the same as what is advertised by rt2x00.
Dec 20 2019
Add kernel config options to sys/conf/options and NOTES