From: Jouni Malinen <j@w1.fi>
To: Sujith <m.sujith@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: Re: [RFC] nl80211: Add frequency configuration (including HT40)
Date: Wed, 26 Nov 2008 09:55:07 +0200 [thread overview]
Message-ID: <20081126075507.GB31499@jm.kir.nu> (raw)
In-Reply-To: <18732.54720.739365.435163@localhost.localdomain>
On Wed, Nov 26, 2008 at 10:21:12AM +0530, Sujith wrote:
> Jouni Malinen wrote:
> > + * @NL80211_ATTR_WIPHY_FREQ: frequency of the selected channel in MHz
> > + * @NL80211_ATTR_WIPHY_SEC_CHAN_OFFSET: included with NL80211_ATTR_WIPHY_FREQ
> > + * if HT40 (40 MHz channels) are allowed:
> > + * NL80211_SEC_CHAN_BELOW = secondary channel is below the primary channel
> > + * NL80211_SEC_CHAN_ABOVE = secondary channel is above the primary channel
>
> The driver needs to know if the selected channel is HT or not.
> It receives only HT20/HT40+/HT40- flags, but a HT/non-HT flag is required too.
Yes, indeed. I added a new enum value for that:
NL82011_SEC_CHAN_NO_HT = no HT (this is the default if
NL80211_ATTR_WIPHY_SEC_CHAN_OFFSET is not included)
NL80211_SEC_CHAN_DISABLED = HT20 only
NL80211_SEC_CHAN_BELOW = HT40-
NL80211_SEC_CHAN_ABOVE = HT40+
The driver will then get hw.conf.ht.{enabled,sec_chan_offset} with the
needed information.
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2008-11-26 7:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 19:05 [RFC] nl80211: Add frequency configuration (including HT40) Jouni Malinen
2008-11-25 19:13 ` Johannes Berg
2008-11-26 7:52 ` Jouni Malinen
2008-11-26 4:51 ` Sujith
2008-11-26 7:55 ` Jouni Malinen [this message]
2008-11-26 8:05 ` Sujith
2008-11-26 8:40 ` Johannes Berg
2008-11-26 9:51 ` Sujith
2008-11-26 8:38 ` Jouni Malinen
2008-11-26 11:04 ` Johannes Berg
2008-11-26 13:14 ` Jouni Malinen
2008-11-26 13:38 ` Jouni Malinen
2008-11-26 13:55 ` Johannes Berg
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=20081126075507.GB31499@jm.kir.nu \
--to=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=m.sujith@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