From: "Jouni Malinen" <jkm@devicescape.com>
To: Jiri Benc <jbenc@suse.cz>
Cc: Michael Wu <flamingice@sourmilk.net>,
Larry Finger <larry.finger@lwfinger.net>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH V3] mac80211: Set low initial rate in rc80211_simple
Date: Fri, 8 Jun 2007 07:58:21 -0700 [thread overview]
Message-ID: <20070608145821.GD14078@devicescape.com> (raw)
In-Reply-To: <20070608112146.2df3608c@griffin.suse.cz>
On Fri, Jun 08, 2007 at 11:21:46AM +0200, Jiri Benc wrote:
> On Thu, 7 Jun 2007 22:05:21 -0700, Michael Wu wrote:
> > On Thursday 07 June 2007 20:49, Larry Finger wrote:
> > > Does mode->rates[0].flags automatically have IEEE80211_RATE_SUPPORTED set?
> > > That wasn't clear to me.
> > >
> > Yes. (see ieee80211_prepare_rates)
>
> No :-) In theory, you can use PRISM2_HOSTAPD_SET_RATE_SETS ioctl to
> disable the lowest available rate. Yes, that's deprecated and bad thing
> to do; but unfortunately, it can be done with the current code.
There are some odd cases, where disabling the lowest supported rate may
even be required due to regulatory rules.. Regardless of whether it is
considered bad thing or not in general, I would hope that this
functionality remains and all rate control algorithms prepare to handle
such an anomaly.
> Larry's patch is IMHO correct.
Agreed.
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2007-06-08 14:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 3:03 [PATCH V3] mac80211: Set low initial rate in rc80211_simple Larry Finger
2007-06-08 3:38 ` Michael Wu
2007-06-08 3:49 ` Larry Finger
2007-06-08 5:05 ` Michael Wu
2007-06-08 9:21 ` Jiri Benc
2007-06-08 14:58 ` Jouni Malinen [this message]
2007-06-08 18:12 ` Luis R. Rodriguez
2007-06-08 18:34 ` Jouni Malinen
2007-06-08 20:10 ` Luis R. Rodriguez
2007-06-08 21:45 ` Jouni Malinen
2007-06-08 16:35 ` Michael Wu
2007-06-11 17:31 ` John W. Linville
2007-06-11 18:11 ` Michael Wu
2007-06-11 18:43 ` John W. Linville
2007-06-11 19:09 ` Michael Wu
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=20070608145821.GD14078@devicescape.com \
--to=jkm@devicescape.com \
--cc=flamingice@sourmilk.net \
--cc=jbenc@suse.cz \
--cc=larry.finger@lwfinger.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).