linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
	Kathy Giori <Kathy.Giori@Atheros.com>,
	Amod Bodas <Amod.Bodas@Atheros.com>,
	David Quan <David.Quan@Atheros.com>,
	Michael Green <Michael.Green@Atheros.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 0/8] wireless: DFS region support
Date: Wed, 5 Jan 2011 10:28:38 -0800	[thread overview]
Message-ID: <20110105182838.GC10391@tux> (raw)
In-Reply-To: <20110104184928.GA13239@tuxdriver.com>

On Tue, Jan 04, 2011 at 10:49:28AM -0800, John W. Linville wrote:
> On Mon, Dec 20, 2010 at 12:02:26PM -0500, Luis R. Rodriguez wrote:
> > This series has a list of changes to kernel and userspace to start addressing
> > DFS region support. I've cheated and figured out a way to alter the current
> > regulatory database in such a way that it remains backwards compatible with
> > older databases so that no new CRDAs are required and we don't have to provide
> > two releases for old kernels and newer kernels for wireless-regdb updates.
> > 
> > In the end we end up passing the DFS region to the drivers. In terms of our DFS
> > development roadmap this covers parts I and II as promissed that I would take care
> > of by tomorrow, and leaves open now the chance for developers to start working
> > on part III: "Where do we stuff DFS parameters for each region":
> > 
> > http://wireless.kernel.org/en/developers/DFS
> > 
> > In tomorrow's meeting we can cover who is going to work on part III. People who
> > want to work on part III can start using these patches on their systems.
> > 
> > John, lets wait to merge these until Wednesday, I post these in patch form as I
> > think they are ready but tomorrow's discussions may push us to alter this a
> > bit, not sure. I will also review what we have done here with Michael Green so
> > he is on the same page.
> 
> Well, now there has been plenty of time to reflect...comments? :-)

I'll reduce the number of bits to 8 instead of 16 for the DFS regions, I'll also
try to schedule a call with Michael to finalize his review on this and then I'll
respin and submit again.

  Luis

  reply	other threads:[~2011-01-05 18:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-20 17:02 [PATCH 0/8] wireless: DFS region support Luis R. Rodriguez
2010-12-20 17:02 ` [PATCH 1/8] wireless-regdb: Add DFS bit fields for countries Luis R. Rodriguez
2010-12-22 13:58   ` Johannes Berg
2010-12-22 14:21     ` Luis R. Rodriguez
2010-12-20 17:02 ` [PATCH 1/2] cfg80211: process new country regulatory flags (DFS) Luis R. Rodriguez
2010-12-22 14:02   ` Johannes Berg
2010-12-22 14:29     ` Luis R. Rodriguez
2010-12-20 17:02 ` [PATCH 2/2] cfg80211: pass DFS region to drivers through reg_notifier() Luis R. Rodriguez
2010-12-21 10:53   ` Johannes Berg
2010-12-21 12:43     ` Luis R. Rodriguez
2010-12-22 14:03   ` Johannes Berg
2010-12-22 14:26     ` Luis R. Rodriguez
2010-12-20 17:02 ` [PATCH 4/8] crda: synch up nl80211.h copy file Luis R. Rodriguez
2010-12-20 17:02 ` [PATCH 5/8] crda: synch up nl80211.h header with upstream for country flags Luis R. Rodriguez
2010-12-22 14:02   ` Johannes Berg
2010-12-22 14:36     ` Luis R. Rodriguez
2010-12-20 17:02 ` [PATCH 1/2] iw: fix country print Luis R. Rodriguez
2010-12-20 17:02 ` [RFC 8/8] wireless-regdb: add FCC as the DFS region for US Luis R. Rodriguez
2011-01-04 18:49 ` [PATCH 0/8] wireless: DFS region support John W. Linville
2011-01-05 18:28   ` Luis R. Rodriguez [this message]
2011-01-05 18:30     ` John W. Linville
2011-01-05 21:26       ` 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=20110105182838.GC10391@tux \
    --to=lrodriguez@atheros.com \
    --cc=Amod.Bodas@Atheros.com \
    --cc=David.Quan@Atheros.com \
    --cc=Kathy.Giori@Atheros.com \
    --cc=Luis.Rodriguez@Atheros.com \
    --cc=Michael.Green@Atheros.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).