All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Michael Green <Michael.Green@atheros.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	wireless-regdb@lists.infradead.org,
	Kathy Giori <Kathy.Giori@atheros.com>,
	David Quan <David.Quan@atheros.com>,
	"John W. Linville" <linville@tuxdriver.com>
Subject: Re: Review of EN 301 893 1.5.1 and 1.6.1 changes
Date: Mon, 31 Jan 2011 22:43:45 +0100	[thread overview]
Message-ID: <1296510225.3812.50.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <AANLkTi=b-Tm7r1eODgAQqpQJuimD0+dQkHFB4YV06kES@mail.gmail.com>

Note: this email is on a public list. If you can't tell that from the Cc
line of the email, I'm not sure you should be working in this field. If
you think I'm mocking you, maybe I am :P

On Mon, 2011-01-31 at 13:33 -0800, Luis R. Rodriguez wrote:
> FYI - European conformance spec for 5 GHz Radio LANs has some slight
> modifications which Johannes has pointed out which we have reviewed
> today in consideration for our new DFS design. The skinny is that our
> implementation of using 3 regions are OK and we will move forward with
> that.

I just fear that will not allow us to keep manoeuvring effectively in
the future, because then we need to change all the implementations,
potentially old ones, rather than just updating the database.

I wasn't so much thinking of the pulse patterns though as the other
timings like the airtime allowed to use before moving onto a new
channel.

johannes


WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Michael Green <Michael.Green@atheros.com>,
	wireless-regdb@lists.infradead.org,
	David Quan <David.Quan@atheros.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	"John W. Linville" <linville@tuxdriver.com>,
	Kathy Giori <Kathy.Giori@atheros.com>
Subject: Re: [wireless-regdb] Review of EN 301 893 1.5.1 and 1.6.1 changes
Date: Mon, 31 Jan 2011 22:43:45 +0100	[thread overview]
Message-ID: <1296510225.3812.50.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <AANLkTi=b-Tm7r1eODgAQqpQJuimD0+dQkHFB4YV06kES@mail.gmail.com>

Note: this email is on a public list. If you can't tell that from the Cc
line of the email, I'm not sure you should be working in this field. If
you think I'm mocking you, maybe I am :P

On Mon, 2011-01-31 at 13:33 -0800, Luis R. Rodriguez wrote:
> FYI - European conformance spec for 5 GHz Radio LANs has some slight
> modifications which Johannes has pointed out which we have reviewed
> today in consideration for our new DFS design. The skinny is that our
> implementation of using 3 regions are OK and we will move forward with
> that.

I just fear that will not allow us to keep manoeuvring effectively in
the future, because then we need to change all the implementations,
potentially old ones, rather than just updating the database.

I wasn't so much thinking of the pulse patterns though as the other
timings like the airtime allowed to use before moving onto a new
channel.

johannes


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


  reply	other threads:[~2011-01-31 21:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTim3CG+aN9QGhGOfBD9+BSYsgQW_ACC0o+k9H-rt@mail.gmail.com>
     [not found] ` <AANLkTinuFzBMMLd08Zpkf8iGBO-YdM2Ni-KtNCNxuUbT@mail.gmail.com>
2011-01-31 21:33   ` Review of EN 301 893 1.5.1 and 1.6.1 changes Luis R. Rodriguez
2011-01-31 21:33     ` [wireless-regdb] " Luis R. Rodriguez
2011-01-31 21:43     ` Johannes Berg [this message]
2011-01-31 21:43       ` Johannes Berg
2011-01-31 21:49       ` Michael Green
2011-01-31 21:49         ` [wireless-regdb] " Michael Green
2011-01-31 21:51         ` Johannes Berg
2011-01-31 21:51           ` [wireless-regdb] " 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=1296510225.3812.50.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=David.Quan@atheros.com \
    --cc=Kathy.Giori@atheros.com \
    --cc=Michael.Green@atheros.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.