From: Sujith <m.sujith@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Jouni Malinen <j@w1.fi>,
linville@tuxdriver.com, linux-wireless@vger.kernel.org,
Jouni.Malinen@atheros.com, Luis.Rodriguez@atheros.com,
tomas.winkler@intel.com
Subject: Re: [RFC v2] mac80211: fix HT channel selection
Date: Mon, 8 Dec 2008 18:54:47 +0530 [thread overview]
Message-ID: <18749.8223.628121.271121@localhost.localdomain> (raw)
In-Reply-To: <1228742349.22164.82.camel@johannes.berg>
Johannes Berg wrote:
> On Mon, 2008-12-08 at 15:14 +0200, Jouni Malinen wrote:
> > On Mon, Dec 08, 2008 at 03:42:23PM +0530, Sujith wrote:
> >
> > > HT management is done differently for AP and STA modes, unify
> > > to just the ->config() callback since HT is fundamentally a
> > > PHY property and cannot be per-BSS.
> > >
> > > Add a new NL80211 attribute to enable/disable HT (NL80211_ATTR_WIPHY_HT).
> > > NL80211_ATTR_WIPHY_SEC_CHAN_OFFSET now has only the secondary channel
> > > offsets.
> >
> > Looks reasonable to me. Please just make sure this gets in before
> > NL80211_ATTR_WIPHY_SEC_CHAN_OFFSET additions get included in any
> > official kernel release since otherwise this would change the userspace
> > API..
>
> I don't like it because it allows specifying "disabled/_above" and a
> bunch of other invalid combinations.
>
Ok, I'll remove this attribute and just rename enum nl80211_sec_chan_offset to
something else.
Sujith
next prev parent reply other threads:[~2008-12-08 13:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 10:12 [RFC v2] mac80211: fix HT channel selection Sujith
2008-12-08 13:01 ` Johannes Berg
2008-12-08 13:14 ` Jouni Malinen
2008-12-08 13:19 ` Johannes Berg
2008-12-08 13:24 ` Sujith [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-09 8:59 [RFC v2] mac80211: Fix " Sujith
2008-12-09 10:24 ` Johannes Berg
2008-12-09 18:12 ` Sujith
2008-12-11 19:07 ` Johannes Berg
2008-12-12 1:45 ` Sujith
2008-12-11 13:53 ` Johannes Berg
2008-12-12 21:48 ` Johannes Berg
2008-12-09 12:54 Mats Johannesson
2008-12-09 13:14 ` Holger Schurig
2008-12-09 13:31 ` Sujith
2008-12-09 15:16 ` Mats Johannesson
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=18749.8223.628121.271121@localhost.localdomain \
--to=m.sujith@gmail.com \
--cc=Jouni.Malinen@atheros.com \
--cc=Luis.Rodriguez@atheros.com \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=tomas.winkler@intel.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;
as well as URLs for NNTP newsgroup(s).