From: Zhu Yi <yi.zhu@intel.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: hostapd with mac80211 progress
Date: Mon, 03 Mar 2008 15:08:19 +0800 [thread overview]
Message-ID: <1204528099.3087.15.camel@debian.sh.intel.com> (raw)
In-Reply-To: <1204302356.3938.36.camel@johannes.berg>
On Fri, 2008-02-29 at 17:25 +0100, Johannes Berg wrote:
> now that John merged more stuff you should only need the hostapd
> patch and the allow-ap-vlan-modes patch from my kernel series :)
OK. This time is much better. Now I can at least ping my 4965 AP with
below fix.
The removal of mac80211 IEEE80211_CHAN_W_SCAN flag causes channel flag
incompatibility between hostapd and driver. Hostapd expects
HOSTAPD_CHAN_W_SCAN (0x1) to be set for the configured channel while 0x1
means IEEE80211_CHAN_DISABLED in the new mac80211. We should make
ieee80211_channel_flags and HOSTAPD_CHAN_W_xxx compatible. What do you
think? I now just workaround the problem with:
diff --git a/hostapd/hw_features.c b/hostapd/hw_features.c
index c58e1e4..8a7b013 100644
--- a/hostapd/hw_features.c
+++ b/hostapd/hw_features.c
@@ -294,8 +294,7 @@ static int select_hw_mode1(struct hostapd_iface
*iface)
for (j = 0; j < iface->current_mode->num_channels; j++) {
struct hostapd_channel_data *chan =
&iface->current_mode->channels[j];
- if ((chan->flag & HOSTAPD_CHAN_W_SCAN) &&
- (chan->chan == iface->conf->channel)) {
+ if (chan->chan == iface->conf->channel) {
ok = 1;
break;
}
next prev parent reply other threads:[~2008-03-03 7:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 9:17 hostapd with mac80211 progress Zhu Yi
2008-02-28 14:06 ` John W. Linville
2008-02-28 14:54 ` Johannes Berg
2008-02-29 6:22 ` Zhu Yi
2008-02-29 15:47 ` Johannes Berg
2008-02-29 16:25 ` Johannes Berg
2008-03-03 7:08 ` Zhu Yi [this message]
2008-03-03 9:52 ` Johannes Berg
2008-03-04 2:03 ` Zhu Yi
2008-03-04 10:00 ` Johannes Berg
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=1204528099.3087.15.camel@debian.sh.intel.com \
--to=yi.zhu@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.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).