linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zefir Kurtisi <zefir.kurtisi@neratec.com>
To: "Rodriguez, Luis" <rodrigue@qca.qualcomm.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	"Presman, Boris" <boris.presman@ti.com>,
	"Azulay, Assaf" <assaf@ti.com>
Subject: Regulatory revamp status
Date: Wed, 28 Sep 2011 17:45:44 +0200	[thread overview]
Message-ID: <4E834128.2030208@neratec.com> (raw)
In-Reply-To: <CAB=NE6UcT8gzVWW+stLEy2SKBCdt-wVnv6aWOZBKTurXk1W0YA@mail.gmail.com>

Hello Luis,

I am referring to your announcement for a regulatory revamp at the LinuxWireless summit in Vancouver and the patches to add DFS information to CRDA you proposed quite some time ago in [1].

For the integration of DFS that is currently being worked out by TI, we will need to have the DFS regulatory domain for the selected countrycode available -- that basically was implemented with the named patch set.

Could you please give some info on the status of the regulatory revamp and particularly if the proposed DFS information will be part of it? One detail that came up in the discussion to your patches was whether DFS regulatory domains are constant for a countrycode or might differ between bands. Has this been clarified meanwhile?



Thanks
Zefir


[1] http://marc.info/?l=linux-wireless&m=129286456607063&w=2, referenced at http://linuxwireless.org/en/developers/DFS#Map_countries_to_a_DFS_region_bit

  reply	other threads:[~2011-09-28 15:53 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 ` Zefir Kurtisi [this message]
2011-09-28 19:52   ` Regulatory revamp status Luis R. Rodriguez
2011-09-29  8:37     ` Zefir Kurtisi
2011-09-29 11:45       ` Adrian Chadd
2011-09-29 12:46         ` Zefir Kurtisi
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=4E834128.2030208@neratec.com \
    --to=zefir.kurtisi@neratec.com \
    --cc=assaf@ti.com \
    --cc=boris.presman@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).