From: Nick Kossifidis <mick@madwifi-project.org>
To: ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org,
linville@tuxdriver.com
Cc: jirislaby@gmail.com, mcgrof@gmail.com, me@bobcopeland.com,
nbd@openwrt.org, j@w1.fi
Subject: [PATCH 5/7] ath5k: Enable AP mode
Date: Thu, 16 Apr 2009 03:36:04 +0300 [thread overview]
Message-ID: <20090416003604.GE4138@makis> (raw)
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).
Author: Jiri Slaby (Jiri added AP support on ath5k, i'm just setting the flag here)
Signed-off-by: Nick Kossifidis <mickflemm@gmail.com>
---
drivers/net/wireless/ath/ath5k/base.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/net/wireless/ath/ath5k/base.c b/drivers/net/wireless/ath/ath5k/base.c
index 6594572..9f080a9 100644
--- a/drivers/net/wireless/ath/ath5k/base.c
+++ b/drivers/net/wireless/ath/ath5k/base.c
@@ -520,6 +520,7 @@ ath5k_pci_probe(struct pci_dev *pdev,
IEEE80211_HW_NOISE_DBM;
hw->wiphy->interface_modes =
+ BIT(NL80211_IFTYPE_AP) |
BIT(NL80211_IFTYPE_STATION) |
BIT(NL80211_IFTYPE_ADHOC) |
BIT(NL80211_IFTYPE_MESH_POINT);
next reply other threads:[~2009-04-16 0:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 0:36 Nick Kossifidis [this message]
2009-04-19 14:42 ` [PATCH 5/7] ath5k: Enable AP mode Bob Copeland
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090416003604.GE4138@makis \
--to=mick@madwifi-project.org \
--cc=ath5k-devel@lists.ath5k.org \
--cc=j@w1.fi \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--cc=me@bobcopeland.com \
--cc=nbd@openwrt.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).