On Fri, Jan 16, 2009 at 01:25:21AM -0800, Johannes Berg wrote: > On Thu, 2009-01-15 at 16:12 -0800, Luis R. Rodriguez wrote: > > When a driver issues a regulatory_hint() lets save the received > > values as original channel settings. This allows users to change > > regulatory domains multiple times while always respecting the driver's > > own regulatory setings. > > This definitely isn't the right way to do things here. This means that > my card that's programmed to US can never do channel 13 here, something > which on b43 we definitely want to allow. Ah -- are you sure you want to allow for that? It seems I was misunderstanding a bit how things would be done for 11d in ath9k and the fact is that we *don't* allow for channels beyond what the programmed regulatory domain allows. This is because calibration stuff has only been tested/ensured/certified/call-it-what you want for the channels in that regulatory domain SKU. Are you certain that b43 can operate well on channels not in their regulatory domain SKU? If so then how about a wiphy flag to let drivers pick this. 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
