Larry Finger wrote:
> 1. The regulatory information is too dynamic to be placed in the kernel.
And not all regulatory information is public: as I wrote in a previous message:
I work for a company that has special regulatory permission to use channels
outside those freely available with tx power of up to 4W. This is a legitimate
use case that should not be forbidden by a new regdomain framework (I can always
hack around this, but that's just a hack, not a clean solution).
Regarding a user space daemon: keep in mind special use cases like NFSroot over WLAN.
> 2. The regulatory database should be in an ASCII file for easy updating. This database should be
> read by a userspace daemon that reformats the information and supplies it to mac80211 upon demand.
OK.
> 3. There should be some sort of checking to verify that the database has not been hacked to modify
> transmission power, etc. in an illegal manner. Obviously, no foolproof means of enforcing this does
> not exist; however, we should prevent the crudest form of modifications.
Define "illegal manner". For me it is perfectly legal to use channel 14 in Europe with 4W tx power. I admit that this is a
special interest, but nonetheless perfectly legal.
--
Regards
Joerg
__________________________________ Yahoo! Clever - Der einfachste Weg, Fragen zu stellen und Wissenswertes mit Anderen zu teilen. www.yahoo.de/clever
-
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
