On Wed, Jan 05, 2011 at 10:28:38AM -0800, Luis R. Rodriguez wrote: > 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. Well, since Linus released 2.6.37 yesterday there is now no great hurry... John -- John W. Linville Someday the world will need a hero, and you linville@xxxxxxxxxxxxx might be all we have. Be ready. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
