On Thu, Sep 25, 2008 at 8:54 PM, Zhu Yi [off-list ref] wrote:

On Thu, 2008-09-25 at 03:23 -0600, Johannes Berg wrote:

quoted

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.

What a distribution carries has no implications as to what you can
install on your own environment. We have both iw and crda installed in
our test environment, but that's also because we like to focus on
wireless-testing.

If you do development based on 2 previous releases essentially you
will get complaints on the type of patches you post based on this old
stuff.

quoted

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.

CONFIG_WIRELESS_OLD_REGULATORY is a temporary solution, the right
solution for you is to build the regulatory domain with the provided
API as discussed at OLS. Additionally distributions can start picking
up iw and crda. I can also see NetworkManager asking the kernel to set
the regulatory domain just as with iw, based on the user's defined
country somewhere.

  Luis