public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Rostislav Lisovy <lisovy@gmail.com>,
	"Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
	Michal Sojka <sojkam1@fel.cvut.cz>,
	s.sander@nordsys.de, jan-niklas.meier@volkswagen.de,
	Rostislav Lisovy <rostislav.lisovy@fel.cvut.cz>
Subject: Re: [PATCH v2] cfg80211: Try multiple bandwidths when checking usable channels.
Date: Mon, 11 Aug 2014 17:12:05 +0200	[thread overview]
Message-ID: <1407769925.9844.10.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1406205820-18152-1-git-send-email-rostislav.lisovy@fel.cvut.cz> (sfid-20140724_144351_874544_422BC7B4)

On Thu, 2014-07-24 at 14:43 +0200, Rostislav Lisovy wrote:
> Current code checks if at least 20MHz bandwidth is allowed for
> particular channel -- if it is not, the channel is disabled.
> This disables usage of 5/10 MHz channels.
> Another issue with the current code is that it may allow a channel
> with bandwidth which is although less or the same as the "maximum
> bandwidth allowed" but overlaps the border of the band.
> 
> The new approach is that there are multiple checks for one channel --
> one for each bandwidth: 5, 10, 20, 40, 80, 160 MHz (when we hit a
> bandwidth that is not allowed, greater bandwidths are automatically
> disabled as well).  This prevents the following scenario to happen:
> The 5 MHz bandwidth channel at the very end of the band is
> successfully checked to fit which is followed by setting flags
> IEEE80211_CHAN_NO_* according to the maximum bandwidth allowed by the
> particular regulatory rule (which may be greater than the 5 MHz).
> When someone will try to use that particular channel with the maximum
> bandwidth allowed (e.g. 20 MHz), the resulting channel will not be in
> the range of the band anymore (will overlap the border).

I really don't know what to do with this. I don't quite understand
what's going on, to be honest.

Luis?

johannes


      parent reply	other threads:[~2014-08-11 15:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-24 12:43 [PATCH v2] cfg80211: Try multiple bandwidths when checking usable channels Rostislav Lisovy
2014-07-24 12:55 ` Rostislav Lisovy
2014-08-11 15:12 ` Johannes Berg [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=1407769925.9844.10.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=jan-niklas.meier@volkswagen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=lisovy@gmail.com \
    --cc=mcgrof@do-not-panic.com \
    --cc=rostislav.lisovy@fel.cvut.cz \
    --cc=s.sander@nordsys.de \
    --cc=sojkam1@fel.cvut.cz \
    /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