Wireless-regdb Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: wireless-regdb@lists.infradead.org
Subject: Re: [wireless-regdb] [PATCH] regdb: allow 40 MHz on world roaming channels 12/13
Date: Tue, 04 Dec 2012 19:20:23 +0100	[thread overview]
Message-ID: <1354645223.9608.11.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CAB=NE6U2hvFbH_EMQbF+toBKSz6mdWyZhvwJ6UZVD-8ks4gp_g@mail.gmail.com>

On Tue, 2012-12-04 at 10:13 -0800, Luis R. Rodriguez wrote:

> >> When in world roaming mode, allow 40 MHz to be used
> >> on channels 12 and 13 so that an AP that is, e.g.,
> >> using HT40+ on channel 9 (in the UK) can be used.
> >
> > Well, hold on.. this can't possibly work now :(
> >
> > This is what happens when Luis and I disagree ...
> >
> > I thought the bandwidth in a given section means the bandwidth that can
> > be used from this section,
> 
> No, indeed that was the objective.

That's not what's implemented though.

> > Luis implemented it to mean that a channel
> > overlapping any part of that section can only use that much bandwidth.
> 
> This was a side effect of the checks we have in place, it was not expected.

But this is what happens due to the reg.c implementation -- it checks
that the freqband into which the primary and secondary channel fall each
allows 40 MHz, even if they are two different freqbands.

> > Note sure which was intended?
> 
> Technically speaking the math should be possible to figure out to
> enable HT40 or not based on peer channels and although that was
> assumed the user reported it not allowing HT40 due to the peer
> channels not allowing HT40. I took your patch as an assumption that
> was not possible.

Indeed this is what we had, but I built the db.txt parser based on the
assumption that in fact "@ 20" in the channel 11/12 freqband would have
been sufficient to allow 40 Mhz on channel 9+. This isn't the case in
the kernel implementation today.

johannes


_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb


  reply	other threads:[~2012-12-04 18:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-12  9:51 [wireless-regdb] [PATCH] regdb: allow 40 MHz on world roaming channels 12/13 Johannes Berg
2012-12-04 14:52 ` Johannes Berg
2012-12-04 16:11   ` John W. Linville
2013-02-12 11:29     ` Johannes Berg
2013-02-12 18:24       ` John W. Linville
2013-02-12 18:45         ` Johannes Berg
2012-12-04 17:48 ` Johannes Berg
2012-12-04 18:13   ` Luis R. Rodriguez
2012-12-04 18:20     ` Johannes Berg [this message]
2012-12-04 18:28       ` Luis R. Rodriguez
2012-12-04 18:41         ` Johannes Berg
2012-12-04 18:54           ` Luis R. Rodriguez
2012-12-04 19:11             ` Johannes Berg
2012-12-04 19:21               ` Luis R. Rodriguez

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=1354645223.9608.11.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=mcgrof@gmail.com \
    --cc=wireless-regdb@lists.infradead.org \
    /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