This adds an API to mac80211 to handle scheduling of TXQs and changes the
interface between driver and mac80211 for TXQ handling as follows:
- The wake_tx_queue callback interface includes only the ac number
instead of the TXQ. The driver is expected to retrieve TXQs from
ieee80211_next_txq()
This moves the ath9k driver to use the mac80211 TXQ scheduling and
airtime accounting APIs, removing the corresponding state tracking
inside the driver.
Signed-off-by: Toke Høiland-Jørgensen
---
drivers/net/wireless/ath/ath9k/ath9k.h | 14 --
drivers/net/wireless/ath/ath9k/debug.c |
This adds airtime accounting and scheduling to the mac80211 TXQ
scheduler. A new callback, ieee80211_sta_register_airtime(), is added
that drivers can call to report airtime usage for stations.
When airtime information is present, mac80211 will schedule TXQs
(through ieee80211_next_txq()) in a
This adds airtime statistics to the cfg80211 station dump, and also adds a new
parameter to set the airtime weight of each station. The latter allows userspace
to implement policies for different stations by varying their weights.
Signed-off-by: Toke Høiland-Jørgensen
---
include/net/cfg80211.h
This is an updated version of the patch series to move TXQ scheduling and
airtime fairness scheduling into mac80211. I've only compile tested this
version, but thought it was better to get the conversation moving instead
of being blocked on me.
This addresses most of the comments from the last
According to vendor sdk, vco calibration has to be executed
for each channel configuration whereas mcu calibration has to be
performed during channel scanning. This patch fixes the mt76x0
monitor mode issue since in that configuration vco calibration
was never executed
Fixes: 10de7a8b4ab9
On Fri, Sep 7, 2018 at 4:24 AM Lorenzo Bianconi
wrote:
>
> > Actions like that have caused great problems in the past, as the
> > kernel won't allow channel control of a monitor interface at all when
> > there is a managed interface on the same phy (afaik).
> >
> > But just for fun and codepath
A new release of wireless-regdb (master-2018-09-07) is available at:
https://www.kernel.org/pub/software/network/wireless-regdb/wireless-regdb-2018.09.07.tar.gz
The short log of changes since the 2018-05-31 release is below.
Thanks,
Seth
---
Henrik Laxhuber (1):
wireless-regdb: update
On Fri, Sep 07, 2018 at 06:28:41PM +0200, Xose Vazquez Perez wrote:
> Cc: Seth Forshee
> Cc: WIRELESS ML
> Cc: REGDB ML
> Signed-off-by: Xose Vazquez Perez
Applied, thanks!
On Fri, Sep 07, 2018 at 07:32:56AM -0500, Seth Forshee wrote:
> On Thu, Sep 06, 2018 at 04:13:22PM +0200, Henrik Laxhuber wrote:
> > Update to reflect the current data published in the 'National Frequency
> > Allocation Strategy Table' [0] for Switzerland and Liechtenstein, which
> > at the time
Cc: Seth Forshee
Cc: WIRELESS ML
Cc: REGDB ML
Signed-off-by: Xose Vazquez Perez
---
db.txt | 13 +
1 file changed, 5 insertions(+), 8 deletions(-)
diff --git a/db.txt b/db.txt
index b168f59..54479fc 100644
--- a/db.txt
+++ b/db.txt
@@ -311,9 +311,10 @@ country CR: DFS-FCC
On Thu, Sep 06, 2018 at 04:13:22PM +0200, Henrik Laxhuber wrote:
> Update to reflect the current data published in the 'National Frequency
> Allocation Strategy Table' [0] for Switzerland and Liechtenstein, which
> at the time of writing points to the documents [1] and [2].
>
> [0]
On Thu, Sep 06, 2018 at 04:59:15PM +0300, Jukka Pirinen wrote:
> Viestintävirasto 15 AM/2018 M
> Section 10 Non-specific short range devices
> https://www.finlex.fi/data/normit/32670/Regulation_15AM.pdf
>
> Signed-off-by: Jukka Pirinen
Applied, thanks!
Lorenzo Bianconi writes:
>> From: Randy Dunlap
>>
>> All of the mt76 driver options use its mac80211.o component,
>> which uses led interfaces, so each of them should depend on
>> LEDS_CLASS.
>>
>> Fixes this build error:
>>
>> drivers/net/wireless/mediatek/mt76/mac80211.o: In function
> Actions like that have caused great problems in the past, as the
> kernel won't allow channel control of a monitor interface at all when
> there is a managed interface on the same phy (afaik).
>
> But just for fun and codepath testing here are two test scenarios:
>
> Test 1: "iwconfig t2u mode
> From: Randy Dunlap
>
> All of the mt76 driver options use its mac80211.o component,
> which uses led interfaces, so each of them should depend on
> LEDS_CLASS.
>
> Fixes this build error:
>
> drivers/net/wireless/mediatek/mt76/mac80211.o: In function `mt76_led_init':
>
16 matches
Mail list logo
