From: "Jouni Malinen" <jkm@devicescape.com>
To: David Lamparter <lists@diac24.net>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Atheros Turbo modes / API [was: nl80211]
Date: Tue, 12 Jun 2007 20:44:31 -0700 [thread overview]
Message-ID: <20070613034431.GE895@devicescape.com> (raw)
In-Reply-To: <20070609114907.GC10836@charon.n2.diac24.net>
On Sat, Jun 09, 2007 at 01:49:07PM +0200, David Lamparter wrote:
> > + case MODE_ATHEROS_TURBO:
> > Are those Atheros Turbo modes actually useful these days in mac80211? If
> > so we probably should support them in nl80211 too, but I don't really
> > know, I guess Jouni is the only one who ever used them?
> Jouni? Is this (a) still in use, and (b) how should it be made available to
> userspace? We could either add additional modes to nl80211_phymode -or- add
> a NL80211_ATTR_ATHEROS_TURBO as boolean tag -or- plunge it into debugfs...
Well, some people may use Atheros Turbo mode, but taken into account
that this is a vendor specific extension and 802.11n will take care of
similar enhancements in a standard way, I don't think there is much
point in trying to maintain any level of support for these in mac80211.
For this reason, most of the Atheros specific stuff was already removed
and only some references to the special channels remained. I haven't
bothered importing support for these into hostapd either. Consequently,
I would just go ahead and remove all references to MODE_ATHEROS_TURBO,
MODE_ATHEROS_TURBOG, and related functionality and comments from
mac80211.
--
Jouni Malinen PGP id EFC895FA
prev parent reply other threads:[~2007-06-13 3:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-09 9:07 your nl80211 work Johannes Berg
2007-06-09 11:39 ` David Lamparter
2007-06-09 12:14 ` Johannes Berg
2007-06-09 13:54 ` Dan Williams
2007-06-11 8:16 ` Johannes Berg
2007-06-09 11:49 ` Atheros Turbo modes / API [was: nl80211] David Lamparter
2007-06-13 3:44 ` Jouni Malinen [this message]
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=20070613034431.GE895@devicescape.com \
--to=jkm@devicescape.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=lists@diac24.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.