--- Mark Cave-Ayland mark.cave-ayl...@siriusit.co.uk wrote:
Von: Mark Cave-Ayland mark.cave-ayl...@siriusit.co.uk
Betreff: Re: [ath5k-devel] AP mode support in ath5k
An: Luis R. Rodriguez lrodrig...@atheros.com
CC: Joerg Pommnitz pommn...@yahoo.com, Michael Buesch m...@bu3sch.de,
Joerg Pommnitz wrote:
Luis, Bob, Mark,
can you suggest a known to be working software combination? Might there be a
special problem with AR5212 based cards (PCI ID 168C:0013)?
Is there anything I can help to track down the problem I see?
Regards
Joerg
Hi Joerg,
I've just checked on
Hi everyone,
I have encountered unexpected behaviour of ath5k from compat-wireless 2.6.33.
In monitor mode, my ath5k based monitor interface appears to only
receive a limited subset of frame types (at least acks, beacons, and
probe requests).
It does not receive authentication frames and
On Thu, Mar 11, 2010 at 07:44:33AM -0800, Joerg Pommnitz wrote:
ath5k AP mode is rock stable on 2.6.32, if two patches are
applied.
(Search the list archives). I did not test 2.6.33, yet. But
this release
should include those patches out of the box.
For what it's worth, I described my
From: Bob Copeland m...@bobcopeland.com
The beacon sent gating doesn't seem to work with any combination
of flags. Thus, buffered frames tend to stay buffered forever,
using up tx descriptors.
Instead, use the DBA gating and hold transmission of the buffered
frames until 80% of the beacon