Do you suitably tickle the clock rate definitions for some of the registers?
IIRC (having looked into this stuff in FreeBSD), enabling turbo mode sets
the clock to double-rate, needing changes to some of the registers like ACK
timeout, slot time, SIFS, etc., which operate on clock-ticks rather tha
d'oh, dropped an = sign somehow. It's in my code
On 02/26/11 15:15, Pat Erley wrote:
> This updates the bwmode set operation to actually set bwmode,
> rather than just returning not supported
>
> Signed-off-by: Pat Erley
> ---
> drivers/net/wireless/ath/ath5k/debug.c | 39
>
I've begun implementing setting the bwmode of compatible ath5k radios.
v1: Add the debugfs entry and implement reading it.
v2: Add setting action. I'm pretty sure my call to reset here is wrong,
anyone know what the 'correct' procedure in this case is? Should I
just check what madwifi di
This adds a bwmode node to the ath5k debugfs directory, adds the
read and write ops, and implements the read op.
Tested on AR5414
Signed-off-by: Pat Erley
---
drivers/net/wireless/ath/ath5k/debug.c | 55
drivers/net/wireless/ath/ath5k/debug.h |1 +
2 files
This updates the bwmode set operation to actually set bwmode,
rather than just returning not supported
Signed-off-by: Pat Erley
---
drivers/net/wireless/ath/ath5k/debug.c | 39 ++-
1 files changed, 37 insertions(+), 2 deletions(-)
diff --git a/drivers/net/wireless/
