... and move dup code from ar5008_phy.c and ar9002_phy.c to phy.c
Signed-off-by: Oleksij Rempel li...@rempel-privat.de
---
drivers/net/wireless/ath/ath9k/Makefile | 1 +
drivers/net/wireless/ath/ath9k/ar5008_phy.c | 144 +--
drivers/net/wireless/ath/ath9k/ar9002_phy.c |
On Fri, May 15, 2015 at 4:38 PM, Julian Calaby julian.cal...@gmail.com wrote:
Hi Oleksij,
On Fri, May 15, 2015 at 10:35 PM, Oleksij Rempel li...@rempel-privat.de
wrote:
... and move dup code from ar5008_phy.c and ar9002_phy.c to phy.c
A better subject might be:
ath9k: consolidate common
Hello, All,
I have a configuration where I want to use an AR9283 device in a Diversity
only scenario (without MIMO). Radio chipset is connected to an AR7241 SoC
and is running OpenWRT Linux distro.
Device is being used as bridged station (Not AP) and has 2 chains,
connected to different
Hi Oleksij,
On Fri, May 15, 2015 at 10:35 PM, Oleksij Rempel li...@rempel-privat.de wrote:
... and move dup code from ar5008_phy.c and ar9002_phy.c to phy.c
A better subject might be:
ath9k: consolidate common phy functions
phy.c doesn't really mean anything to people outside the developers
Am 16.05.2015 um 07:36 schrieb Joe Perches:
On Sat, 2015-05-16 at 07:27 +0200, Oleksij Rempel wrote:
Am 15.05.2015 um 20:35 schrieb Joe Perches:
On Fri, 2015-05-15 at 14:35 +0200, Oleksij Rempel wrote:
... and move dup code from ar5008_phy.c and ar9002_phy.c to phy.c
[]
diff --git
On Sat, 2015-05-16 at 07:27 +0200, Oleksij Rempel wrote:
Am 15.05.2015 um 20:35 schrieb Joe Perches:
On Fri, 2015-05-15 at 14:35 +0200, Oleksij Rempel wrote:
... and move dup code from ar5008_phy.c and ar9002_phy.c to phy.c
[]
diff --git a/drivers/net/wireless/ath/ath9k/phy.c
Am 15.05.2015 um 20:35 schrieb Joe Perches:
On Fri, 2015-05-15 at 14:35 +0200, Oleksij Rempel wrote:
... and move dup code from ar5008_phy.c and ar9002_phy.c to phy.c
[]
diff --git a/drivers/net/wireless/ath/ath9k/phy.c
b/drivers/net/wireless/ath/ath9k/phy.c
+void
Am 15.05.2015 um 21:34 schrieb Felix Fietkau:
On 2015-05-15 14:35, Oleksij Rempel wrote:
... and move dup code from ar5008_phy.c and ar9002_phy.c to phy.c
Signed-off-by: Oleksij Rempel li...@rempel-privat.de
We already have base functionality for AR5008-AR9002 provided in some
ar5008_phy.c,
On 2015-05-16 07:24, Oleksij Rempel wrote:
Am 15.05.2015 um 21:34 schrieb Felix Fietkau:
On 2015-05-15 14:35, Oleksij Rempel wrote:
... and move dup code from ar5008_phy.c and ar9002_phy.c to phy.c
Signed-off-by: Oleksij Rempel li...@rempel-privat.de
We already have base functionality for
On 2015-05-15 14:35, Oleksij Rempel wrote:
... and move dup code from ar5008_phy.c and ar9002_phy.c to phy.c
Signed-off-by: Oleksij Rempel li...@rempel-privat.de
We already have base functionality for AR5008-AR9002 provided in some
ar5008_phy.c, and ar5008_hw_attach_phy_ops is called for those
Thank you Adrian,
Could you point me towards the reference driver? Also, any idea where in
ath9k is a good place to check for decryption failures?
Instrumenting ath9k_cmn_rx_accept in ath9k/common.c showed some decrypt
errors, but it was about same amount for working and broken states.
Alexis
On Fri, 2015-05-15 at 14:35 +0200, Oleksij Rempel wrote:
... and move dup code from ar5008_phy.c and ar9002_phy.c to phy.c
[]
diff --git a/drivers/net/wireless/ath/ath9k/phy.c
b/drivers/net/wireless/ath/ath9k/phy.c
+void phy_hw_spur_mitigate(struct ath_hw *ah,
+ struct
12 matches
Mail list logo