On 9/21/07, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Fri, 2007-09-21 at 17:39 -0400, Dan Williams wrote: > > > Also, if you could make sure this stuff is completely separate > > conceptually and architecturally from mac80211 itself, but have mac80211 > > _rely_ on it, then we can rip the bits out of the fullmac drivers that > > do regdomain stuff and plug them into this framework too. I think > > that's a real win. > > Yeah, I think that's the plan. In fact, I always consider mac80211 to be > on the the same level like fullmac _drivers_ and mac80211-based drivers > somewhere below that (at a level that with fullmac drivers doesn't > exist) Correct, the only way this touches mac80211 is ripping common wireless stuff out from it and putting it into a wireless_common.h. other than that all of this so far is 100% independent of mac80211. In fact, you can apply each patch, one by one, and compile the kernel and all modules and you should have no issues independently. However each subsequent patch depends on the previous patch. The idea with this was to try to get this regulatory work into the 'everything' wireless-dev branch so we can address any small issues before we start hacking away on mac80211 and its drivers. At first I wanted to send all of the patches together but this was just taking too long... My hope now was to speed the development process up by separating the required work into two patches series. Luis - 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
