From: Jiri Benc <jbenc@suse.cz>
To: Michael Wu <flamingice@sourmilk.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"Jouni Malinen" <jkm@devicescape.com>,
netdev@vger.kernel.org, jkmaline@cc.hut.fi
Subject: Re: [PATCH wireless-dev] d80211: Don't discriminate against 802.11b drivers
Date: Fri, 12 May 2006 12:47:03 +0200 [thread overview]
Message-ID: <20060512124703.563dacd6@griffin.suse.cz> (raw)
In-Reply-To: <200605101331.39960.flamingice@sourmilk.net>
On Wed, 10 May 2006 13:31:39 -0400, Michael Wu wrote:
> I think this is overkill to fix a hack. IMHO, scan_skip_11b shouldn't exist in
> the first place. One alternative would be to modify 802.11g drivers to not
> set IEEE80211_CHAN_W_SCAN on 802.11b channels when there are equivalent
> 802.11g channels.
This won't work when 11g is administratively disabled. We can surely add
another flags; but I'm not sure if it is really desirable to require
drivers to be aware of this when it is easily determinable by the stack.
> It seems like hw_modes is more useful for saying
> what modes shouldn't be used than saying what modes are supported by the
> hardware and should be used.
This is exactly the purpose of hw_modes. This also means you don't need
any validation.
Jiri
--
Jiri Benc
SUSE Labs
next prev parent reply other threads:[~2006-05-12 10:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 2:32 [PATCH wireless-dev] d80211: Don't discriminate against 802.11b drivers Michael Wu
2006-05-11 15:54 ` Jiri Benc
2006-05-10 17:31 ` Michael Wu
2006-05-12 10:47 ` Jiri Benc [this message]
2006-05-12 20:35 ` Michael Wu
2006-05-15 11:37 ` Jiri Benc
2006-05-15 12:04 ` Johannes Berg
2006-05-15 13:35 ` Jiri Benc
2006-05-15 14:01 ` Michael Buesch
2006-05-15 14:12 ` Jiri Benc
2006-05-15 17:19 ` Michael Wu
2006-05-19 18:06 ` John W. Linville
2006-05-19 19:03 ` Michael Wu
2006-05-19 19:22 ` John W. Linville
2006-05-11 20:41 ` Michael Buesch
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=20060512124703.563dacd6@griffin.suse.cz \
--to=jbenc@suse.cz \
--cc=flamingice@sourmilk.net \
--cc=jkm@devicescape.com \
--cc=jkmaline@cc.hut.fi \
--cc=linville@tuxdriver.com \
--cc=netdev@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).