On Thu, 2008-09-25 at 03:23 -0600, Johannes Berg wrote: > Not that I understand why you need that since iw shows all channels > you > are registering (albeit with possibly a few more flags like > "disabled"), > but yeah, if anything all this stuff should be in debugfs. The real user for the function is the automated test cases of our validation team running nightly. Greppig dmesg is not reliable and iw is not mature enough (at least not included in major distros). We will move it to debugfs for now. After iw is as common as iwconfig, we will eventually remove this. > There's also > this little fact that this channel list shouldn't ever get used, you > should be (and afaik are since I fixed it) using what the regdomain is > enforcing, and you're already printing the channel list when enough > debugging flags are set on driver load. This is used for debugging especially during the time regdomain is under development. I've received quite a few bug reports that is due to CONFIG_WIRELESS_OLD_REGULATORY is not enabled. I need at least a way to tell the users this is due to your misconfig your regdomain or your hardware is not capable to work on that channel. Thanks, -yi -- 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
