On Sun, Oct 19, 2008 at 11:50 PM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Sun, 2008-10-19 at 23:46 -0700, Luis R. Rodriguez wrote: > >> Sure but an issue here is that if we do deal with band-specific >> regulatory domain definitions we change the regulatory behavior from >> being "disallow everything first" to "allow everything first, disable >> everything in the band for which we encounter a rule in except what >> the rule allows". >> >> Since the regulatory definitions in db.txt are in KHz we are allowing >> it to grow as more technology pops up with support for more bands. I >> think the first approach was better. The current suggestion of only >> applying rules if a band reg definition is present is only to deal >> with a rare case. I think its better we try to handle that instead and >> keep our existing behaviour. > > Ack on both points, which is why I said "If we're going to [...]". I > don't think I've seen a convincing use case for this other than test > environments, in which you can very well just use crda. Ah, ok :) Yi, BTW a simple way to get a distribution to add support initially for crda is to have as part of an init script to call iw reg set $COUNTRY where $COUNTRY is determined though whatever distribution heuristics. 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
