All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zefir Kurtisi <zefir.kurtisi@neratec.com>
To: Adrian Chadd <adrian@freebsd.org>
Cc: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Boris Presman <boris.presman@ti.com>, Assaf Azulay <assaf@ti.com>,
	Michael Green <green@qca.qualcomm.com>,
	David Quan <dquan@qca.qualcomm.com>,
	Kevin Hayes <hayes@qca.qualcomm.com>,
	Arun Venkataraman <arunvenk@qca.qualcomm.com>
Subject: Re: Regulatory revamp status
Date: Thu, 29 Sep 2011 14:46:39 +0200	[thread overview]
Message-ID: <4E8468AF.8000006@neratec.com> (raw)
In-Reply-To: <CAJ-VmonqEs4mODDa2=fTj8zWHwRM7-G5e=BWNUyGdy65+kYvfg@mail.gmail.com>

On 09/29/2011 01:45 PM, Adrian Chadd wrote:
> On 29 September 2011 16:37, Zefir Kurtisi <zefir.kurtisi@neratec.com> wrote:
>> Thanks for the update.
>>
>> To me it looks not reasonable to mix in between the two approaches: either we assume countrycodes use the same DFS region for all channels, or each channel/band needs to have its own. Otherwise I feel that a DFS region bitmap would give a semi-flexible compromise that might end up being insufficient to represent some fancy countrycodes.
> 
> There's some funny stuff in there.
> 
> For example, some of the DFS bands have different CAC/NOL timing. :-)
> 
> 
> 
> Adrian

Really? Where would be 'there' countrycode-wise?

That would definitely break today's CRDA capabilities :-\


Zefir

  reply	other threads:[~2011-09-29 12:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24 23:11 Regulatory simulator - regulatory revamp work Luis R. Rodriguez
2011-09-28 15:45 ` Regulatory revamp status Zefir Kurtisi
2011-09-28 19:52   ` Luis R. Rodriguez
2011-09-29  8:37     ` Zefir Kurtisi
2011-09-29 11:45       ` Adrian Chadd
2011-09-29 12:46         ` Zefir Kurtisi [this message]
2011-09-29 17:47           ` Luis R. Rodriguez
2011-09-30 11:11             ` Zefir Kurtisi
2011-09-30 11:21           ` Adrian Chadd
2011-09-30 12:52             ` Zefir Kurtisi
2011-10-03 20:00       ` 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=4E8468AF.8000006@neratec.com \
    --to=zefir.kurtisi@neratec.com \
    --cc=adrian@freebsd.org \
    --cc=arunvenk@qca.qualcomm.com \
    --cc=assaf@ti.com \
    --cc=boris.presman@ti.com \
    --cc=dquan@qca.qualcomm.com \
    --cc=green@qca.qualcomm.com \
    --cc=hayes@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rodrigue@qca.qualcomm.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 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.