From: Johannes Berg <johannes@sipsolutions.net>
To: Mahesh <maheshp@posedge.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [RFC] cfg80211: 80Mhz Bandwidth channel flags in 5Gig band
Date: Wed, 22 Feb 2012 19:57:52 +0100 [thread overview]
Message-ID: <1329937072.4657.4.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1329933458.4657.2.camel@jlt3.sipsolutions.net> (sfid-20120222_185746_860409_0CF57D5F)
On Wed, 2012-02-22 at 18:57 +0100, Johannes Berg wrote:
> On Wed, 2012-02-22 at 23:21 +0530, Mahesh wrote:
> > This change is for marking 80Mhz bandwidth supported channel flags in
> > 5Gig band.
>
> This patch is not only completely mangled, it also neglects to actually
> support this in the regdb etc. What's the point?
I should elaborate. Something like this code is needed, but right now
the regulatory database contains things like
(5150 - 5350 @ 40), (N/A, 100 mW), NO-OUTDOOR, DFS
which means at most 40 MHz can be used.
In your patch, you don't even check this maximum bandwidth, which is a
bug, but even if you did the database would have to be changed.
Also, we probably really need to introduce handling of spectral power
limits to make this worthwhile?
johannes
next prev parent reply other threads:[~2012-02-22 18:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 17:51 [RFC] cfg80211: 80Mhz Bandwidth channel flags in 5Gig band Mahesh
2012-02-22 17:57 ` Johannes Berg
2012-02-22 18:57 ` Johannes Berg [this message]
2012-02-24 5:25 ` [RFCv2] " Mahesh
2012-02-24 5:43 ` Adrian Chadd
2012-02-24 5:48 ` Mahesh
2012-02-24 8:01 ` Johannes Berg
2012-02-24 7:55 ` Johannes Berg
2012-02-24 11:21 ` Mahesh
2012-02-25 19:22 ` Adrian Chadd
2012-02-25 21:30 ` Johannes Berg
[not found] ` <eab3dfdc8ebc87ec08ca64db9f237d90@posedge.com>
2012-04-03 12:06 ` 802.11ac support Johannes Berg
2012-04-03 12:11 ` Johannes Berg
2012-04-05 4:21 ` Mahesh
2012-04-05 14:06 ` 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=1329937072.4657.4.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=maheshp@posedge.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).