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 20:11:15 +0100	[thread overview]
Message-ID: <1354648275.9608.18.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CAB=NE6UMvx4uRxy9nTxZX6fCC=jPoxoF-mKdL=pvBVwH3cR+QA@mail.gmail.com>

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

> >> As I implemented it, it should be checking if HT40 is used. If so then
> >> it should be checking to see if the primary can use 40 MHz bandwidth
> >> and then check to see if the secondary can use 20 MHz. The issue
> >> should be that the code should likely is checking that the secondary
> >> requires 40 MHz. It should only need to check if the secondary can use
> >> 20 MHz if HT40 is desired.
> >
> > I don't think this is really what we should do ... In fact given the way
> > we do it now with overlapping freqbands this would cause more problems
> > than it would solve, I think.
> 
> If we end up supporting overlapping frequency rules to be submitted.
> Right now they don't overlap but point taken that we do support it and
> there may possible issue of having them supported.

00 has overlapping rules today, also JP and KP

> > What it really should check is that for each freqband, as much bandwidth
> > is allowed as falls into that freqband. But given that we have
> > overlapping freqbands, much bandwidth will actually fall into each one
> > of them, so we must allow @40 again ...
> >
> > I'm drawing some pictures now :-)
> 
> :) Lets be clear though that your points on overlapping frequency
> rules are a separate architectural position to take than addressing
> the issue at hand. This however is a good crux point for us to
> evaluate this particular architectural consideration.

Agree.

johannes


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


  reply	other threads:[~2012-12-04 19:10 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
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 [this message]
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=1354648275.9608.18.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