Linux wireless drivers development
 help / color / mirror / Atom feed
* prism2 "next mode" and its implications
@ 2007-09-28 16:22 Johannes Berg
  0 siblings, 0 replies; only message in thread
From: Johannes Berg @ 2007-09-28 16:22 UTC (permalink / raw)
  To: Jouni Malinen; +Cc: Luis R. Rodriguez, linux-wireless

[-- 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 --]

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2007-09-28 16:21 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-09-28 16:22 prism2 "next mode" and its implications Johannes Berg

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox