08719b1 mt76: use a per rx queue page fragment cache 4d2c565 mt76x2: reset HW before probe f622975 mt76x2: fix CCK protection control frame rate 6780375 mt76x2: add frame protection support Signed-off-by: Felix Fietkau <nbd@nbd.name>
Enables support for Dynack feature. When a remote station is far away, we need to compensate for the distance by allowing more time for an ACK to arrive back before issueing a retransmission. Currently, it needs to be set fixed to indicate the maximum distance the remote station will ever be. While this mostly works for static antennae, it introduces 2 issues: - If the actual distance is less, speed is reduced due to a lot of wates wait-time - If the distance becomes greater, retries start to occur and comms can get lost. Allowing to set it dynamically using dynack ensures the best possible tradeoff between speed vs distance. This feature is currently only supported in ath9k. it is also disabled by default. Enabling it can be done in 2 ways: - issue cmd: iw phy0 set distance auto - sending the NL80211_ATTR_WIPHY_DYN_ACK flag to mac80211 driver using netlink Disabling it can be done by providing a valid fixed value. To give an idea of a practical example: In my usecase, we have mesh wifi device installed on ships/platforms. Currently, the coverage class is set at 12000m fixed. When a vessel moved closer (ex. 1500m), the measured link capacity was a lot lower compared to setting the coverage class fixed to 1500m Dynack completely solved this, nearly providing double the bandwidth at closer range compared to the fixed setting of 12000m being used. Also when a vessel sailed to a distance greater than the fixed setting, communication was lost as the ACK's never arrived within the max allowed timeframe. Actual distance: 6010m iperf 60s run avg Fixed 12150m: 31 Mbit/s Dynack: 58 Mbit/s Fixed 6300m: 51 Mbit/s Dynack: 59 Mbit/s Fixed 3000m: 13 Mbit/s (lots of retries) Dynack: 58 Mbit/s Actual distance: 1504m iperf 60s run avg Fixed 12150m: 31 Mbit/s Dynack: 86 Mbit/s Fixed 6300m: 55 Mbit/s Dynack: 87 Mbit/s Fixed 3000m: 67 Mbit/s Dynack: 87 Mbit/s Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
Most of the implementations behind cfg80211_get_station will not initialize sinfo to zero before manipulating it. For example, the member "filled", which indicates the filled in parts of this struct, is often only modified by enabling certain bits in the bitfield while keeping the remaining bits in their original state. A caller without a preinitialized sinfo.filled can then no longer decide which parts of sinfo were filled in by cfg80211_get_station (or actually the underlying implementations). cfg80211_get_station must therefore take care that sinfo is initialized to zero. Otherwise, the caller may tries to read information which was not filled in and which must therefore also be considered uninitialized. In batadv_v_elp_get_throughput's case, an invalid "random" expected throughput may be stored for this neighbor and thus the B.A.T.M.A.N V algorithm may switch to non-optimal neighbors for certain destinations. Signed-off-by: Sven Eckelmann <sven.eckelmann@openmesh.com> (cherry picked from commit 87493dac11f3c7bbbc1fed9aef1cf9ff62053ab0)
Board Data File (BDF) is loaded upon driver boot-up procedure. The right
board data file is identified on QCA4019 using bus, bmi-chip-id and
bmi-board-id.
The problem, however, can occur when the (default) board data file cannot
fulfill the vendor requirements and it is necessary to use a different
board data file.
This problem was solved for SMBIOS by adding a special SMBIOS type 0xF8.
Something similar has to be provided for systems without SMBIOS but with
device trees. No solution was specified by QCA and therefore a new one has
to be found for ath10k.
The device tree requires addition strings to define the variant name
wifi@a000000 {
status = "okay";
qcom,ath10k-calibration-variant = "RT-AC58U";
};
wifi@a800000 {
status = "okay";
qcom,ath10k-calibration-variant = "RT-AC58U";
};
This would create the boarddata identifiers for the board-2.bin search
* bus=ahb,bmi-chip-id=0,bmi-board-id=16,variant=RT-AC58U
* bus=ahb,bmi-chip-id=0,bmi-board-id=17,variant=RT-AC58U
Signed-off-by: Sven Eckelmann <sven.eckelmann@open-mesh.com>
(cherry picked from commit 1c01e02575bd2af96741ba79ed12004fdfb15544)
Fixes a potential infinite loop bug when in unlimited (ie not using built in shaper) mode. Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk> (cherry picked from commit 4bd4ece9eafbcde62d1e6efc4cf820f05906dd28)
This bumps to the latest & possibly greatest cake, sadly it's still inedible but from an SQM point of view quite tasty :-) Main tweaks since previous bump, improved ack_filter, some extra stats, support for 64bit netlink parameters (higher rates/byte counters) 0520a6c Fix NAT option handling 8da93e1 Make sure we always call qdisc_watchdog_init() in cake_init() f65daf6 Fix mismatched parenthesis 51d4ab3 Change flag handling to be safe even when mixing with non-eligible ACKs f2ea091 ack_filter: protect DCTCP with stricter filtering of ECE marks 28b4560 ACK filter: Handle wrapping sequence numbers and DSACKs 73f62d9 Use the right PAD attribute for options 5969c14 Use 32 for tin backlog e289f31 Move all the u64 netlink attributes together 36180a0 Check ACK seqno before parsing SACKs 91bbc01 Merge branch 'mine' into cobalt 58c55ec Rework SACK check to compare the ranges of two SACKs 9a5d593 ack_filter: Add proper handling of SACKs eca95d4 ack_filter: short-circuit TCP flag check d50a246 compat: backport some ktime functions 7b7ad11 compat: define tcpopt_fastopen for pre-4.1 kernels ca54cdb Fix ktime compare 9d7dcc0 ack filter: Parse TCP options and only drop safe ones b119882 Return EOPNOTSUPP on NAT option if conntrack is not available 842d7f0 Don't try to pad stats with tin_stats padding bd46dc2 Use 64-bit divide helper 8e41bf0 Make sure we never drop SACKs when filtering ACKs 66e5d60 Avoid comparing ktime_t to scalar values 7fab017 Actually commit the ktime_t changes fca6d13 Switch to ktime_t and get rid of cobalt.h 6f7e5af Can't use do_div with 64-bit divisors Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk> (cherry picked from commit abeae38dbbe8b7fda10ad36fb5db57ed16c93479)
we only wanted to drop rtl8xxxue support Signed-off-by: John Crispin <john@phrozen.org> (cherry picked from commit d8981133b27e7deebc79dc5fc51beb06b3b0a221)
After a very enlightening but unfortunately far too short exchange with Jes we mutually agreed to drop the patches. They are unfortunately not ready yet. Acked-by: Rafał Miłecki <rafal@milecki.pl> Signed-off-by: John Crispin <john@phrozen.org> (cherry picked from commit 66c5696cdf9599ccef652a651f52c0f7f53da44a)
Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit c446e38c862201dd4d6a4fb8ea6e49172980952d)
It backports remaining brcmfmac changes from 4.17. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 7e8eb7f309a802ba10a13ddb807c6a31fecc9183)