• J
    ath5k: Enable AP mode · 6f5f39c9
    Jiri Slaby 提交于
    After some debuging we were hitting the following bugs so far...
    
     * Due to huge channel list hostapd couldn't get infos from the driver
     and couldn't set the channel. If we manualy set the channel after
     hostapd starts (by setting channel to 0 -auto), beacons are sent
     but they wont show up on scan because they are malformed (they have
     channel = 0 because hostapd doesn't update the channel info -this is
     probably a hostapd bug so i'm CCing Jouni) and they get dropped. Bob
     fixed this by only allowing standard channels to be registered so
     now hostapd works as expected.
    
     * Docs (and HAL source) say that we must write 0 on timer0 when
     operating on AP mode to start TSF increment but this seems to
     mess with DBA in many cases and beacon queue never gets started.
     We fixed that on the previous patch.
    
     We have some more things to deal with...
    
     * For some reason (hw bug or something else) after restarting hostapd
     a few times, beacon inteval seems to change from 100ms to a sec
     (we get one beacon per sec).
    
     * We need to set sleep timers on STA mode and enable power saving +
     support PCF.
    
     ...but i think it's time we enable AP support "officialy" so that
     we can get more feedback from users. I ran ath5k with the mentioned
     patches + hostapd 0.6.8 and AP mode worked fine (it had some less
     throughput on my tests than IBSS but it worked).
    Signed-off-by: NNick Kossifidis <mickflemm@gmail.com>
    Signed-off-by: NBob Copeland <me@bobcopeland.com>
    Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
    6f5f39c9
base.c 82.3 KB