On 10/24/06, David Kimdon <[EMAIL PROTECTED]> wrote:
Hi,
> The following patches extend 802.11 regulatory domain support of the
> d80211 wireless stack through two modules:
>
> 1. ieee80211_regdomains
> 2. iso3166-1
I am glad to see this work, this is something that we need a solution
for. I do wonder if we can push most of this out of the kernel and
into userspace. We could hard code a single set of constraints in the
kernel which may be used world wide (802.11b channels 1-11, is that
allowed everywhere?).
Unforunatley there is no easy middle ground that will make everyone
happy. What I defined as World is there just as most devices seem to
have such regulatory domain and what I defined it as is a compromise
in what seems to be the middle of all restrictions. There is no easy
answer here but I think the best is to consider that there is just no
"World" regulatory domain unless all regulatory domain agencies do
come up with one. We should see if legal can work with a few
regulatory agencies to see if at least a few will agree on one...
Then we have a userspace tool which passes
updated regulatory information into the kernel based on the user's
country input.
Please see my more thorough reply to Johannes as he asked this first.
But yes -- you are right. The main reason why this has been put in the
kernel was to make a userspace daemon optional as it would allow us to
easily introduce regulatory domain control without forcing
distributions to use a new daemon immediately. Also we need to iron
out userspace communication before even considering a userspace
regulatory daemon. Keep in mind the Kconfig makes the regulatory
domains defined optional except World compliant regulatory domain
already.
Luis
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
