From: Johannes Berg <johannes@sipsolutions.net>
To: Jouni Malinen <j@w1.fi>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: prism2 "next mode" and its implications
Date: Fri, 28 Sep 2007 18:22:51 +0200 [thread overview]
Message-ID: <1190996571.22960.12.camel@johannes.berg> (raw)
[-- Attachment #1: Type: text/plain, Size: 833 bytes --]
Hey,
Just was discussing this with Luis as he's implementing all the new
regulatory stuff.
We used to have a prism2 ioctl to set "next mode" for channel selection
so that when selecting a channel you'd be able to select, say, channel 5
(freq 2412 MHz) on B mode.
Then, when thinking about nl80211, I figured that any "set channel"
command/attribute should go along with a "mode" attribute so we can
distinguish this.
Now, however, I'm no longer convinced this is the right thing to do. If
we're a station, then the supported bitrates are determined by the
hardware and the AP anyway. And if we're an AP, wouldn't it make more
sense to set the bitrates explicitly? We already need to set the basic
rates anyway, and we also already set the slot timing, so I don't see
what setting the mode buys us.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
reply other threads:[~2007-09-28 16:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1190996571.22960.12.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=j@w1.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
/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