Re: New Regulatory Domain Api.

[Zhu Yi <yi.zhu@intel.com>]

On Thu, 2008-10-09 at 09:45 -0600, Luis R. Rodriguez wrote:
> 
> In your case I think you hit this after rmmod and modprobe:
> 
>         if (last_request->wiphy != wiphy)
>                 return -EALREADY;
> 
> since the last wiphy != your new wiphy. The reason this check was
> added
> though, as the comment indicates, was to prevent two drivers with
> different regulatory domains from trying to set it. In your case this
> doesn't affect your requested setting as the old regulatory domain
> is still set. This check currently also forces the first device
> detected
> on the system and its regutory_hint() to be respected over any other
> devices considering that your built in wireless card on your laptop
> will probably be detected first over your cardbus card, or USB card
> for example.
> 
> In other words this you can treat -EALREADY return value as non
> critical, as per the documentation (please see
> include/net/wireless.h).

Does below scenario an expected behaviour?

0. A system with iwl3945 BG card and iwl4965 AGN card.
1. insmod iwl3945 -> regulatory_hint(, 99, rd) return 0;
2. insmod iwl4965 -> regulatory_hint(, 99, rd2) return -EALREADY;
3. iwl4965 has no A band support!

Thanks,
-yi