From: Johannes Berg <johannes@sipsolutions.net>
To: Matthias May <matthias.may@neratec.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCHv2 1/4] cfg80211: handle minimum bandwidth for quarter and half rates
Date: Thu, 11 Jun 2015 17:22:29 +0200 [thread overview]
Message-ID: <1434036149.1915.15.camel@sipsolutions.net> (raw)
In-Reply-To: <5579831F.3020304@neratec.com>
On Thu, 2015-06-11 at 14:46 +0200, Matthias May wrote:
> Using the dummy country code:
> country XS: DFS-UNSET
> (5170 - 5180 @ 5), (N/A, 14), (N/A)
> (5175 - 5185 @ 10), (N/A, 17), (N/A)
> (5170 - 5190 @ 20), (N/A, 20), (N/A)
>
> For a center freq of 5175
> The first loop finds the first rule. --> we want this.
> The second loop doesn't find anything.
> The third loop doesn't find anything.
>
> However for a center freq of 5180
> The first loop find the first rule
> The second loop find the second rule
> The third loop find the third rule. --> We want this
>
> If there are different overlapping rules for the different bandwidths
> different results can be returned, especially at the border of a
> frequency range.
Hmmm. Can we just forbid those overlapping rules, and say you want
AUTO-BW?
I mean, do you see a reason for this otherwise?
johannes
next prev parent reply other threads:[~2015-06-11 15:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 11:06 [PATCHv2 0/4] Handle minimum bandwidth for quarter and half rates Matthias May
2015-06-11 11:06 ` [PATCHv2 1/4] cfg80211: handle " Matthias May
2015-06-11 11:33 ` Johannes Berg
2015-06-11 11:44 ` Johannes Berg
2015-06-11 12:46 ` Matthias May
2015-06-11 15:22 ` Johannes Berg [this message]
2015-06-11 11:06 ` [PATCHv2 2/4] ath: send minimum bandwidth to handle Matthias May
2015-06-11 11:06 ` [PATCHv2 3/4] brcm80211: " Matthias May
2015-06-11 11:06 ` [PATCHv2 4/4] rtlwifi: " Matthias May
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=1434036149.1915.15.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=matthias.may@neratec.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).