Re: New Regulatory Domain Api.

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

On Mon, 2008-10-20 at 23:02 -0700, Luis R. Rodriguez wrote:
> The issue at hand, which started this 60-message thread, involves a
> built-in Intel single band 2 GHz card and an external dual band card.
> The issue is the dual band card's regulatory_hint() is ignored as the
> current infrastructure ignores secondary requests and the first one
> did not define a set of rules for 5 GHz as part of its
> regulatory_hint(). A resolution to this is to have crda called for the
> country the user is in. 

A suboptimal solution. We all know that. The kernel has to rely on some
help from iw to resolve a problem it has the ablility to resolve itself.

> The reason this solves the issue at and is
> hardware which is designed to not allow channels out of its EEPROM
> won't be enabled as these channels are not registered and channels
> which *should* be disabled based on the user's location *are*
> disabled. The 5 GHz channels on the dual band card which *should* be
> allowed are allowed. Additionally we do allow drivers to be cocky
> about regulatory and to claim they know better through reg_notifier().

Driver's reg_notifier should only disable a channel which the regulatory
framework marks as enabled. But not vice versa. Otherwise your below
case fails.

> If a hardware device has a built in channel 14 and a user in the US
> buys this device and goes to the US he/she should disable this channel
> to remain compliant. Under your current suggestion this is not dealt
> with. That is what I mean by handling outdated rules.

I don't see where it doesn't fit in my model. The driver hints
EVERYTHING after loading. Then the user overwrote it to "US". After
that, channel 14 is forbiddened by reg framework (although driver still
claims it supports it). This is what I said EVERYTHING should always be
overwritten by other regdomains.

Thanks,
-yi