* Daniel Dickinson <dan...@cshore.neomailbox.net> [10.03.2013 19:57]: > Actually, the default in the code is to use the EEPROM values if > present, but if the EEPROM doesn't set a country code or
to be clear: during compile-time, a description is loaded which values are allowed for each country: http://git.kernel.org/?p=linux/kernel/git/linville/wireless-regdb.git;a=blob_plain;f=db.txt;hb=HEAD even if those values are changing (and they do!) you have e device which needs a reflash to get the new values, so in the EEPROM is just the country set and the software/driver knows what to do. e.g. what we make, is to include a changed "regdb" during compiletime. (but ofcourse respect the law) > > > it's the same like block the word "f*ck" in the wordprocessor, > > > because the government forbids it? ok, dont get me wrong, i overact > > > a littly bit, but the hole thing upset's me... > > > > sorry, but this is really a different case. > > I concur, this isn't about what you say or write in private, for ok, this was a bad example. > instance. EM interference is a public safety and communications issue > (interfering with emergency frequencies or vital control systems is > obviously bad, and even if it was just television signal, interfering > with everyone else's television because *you* want better wifi is > selfish at best; and messing with cell phones because you want wifi > won't make you friends). > > Telecommunications regulations exist because otherwise it'd be like it's not about breaking the law (no discussion about that needed here) it's about using the values you are allowed, e.g. using channel 12,13 in germany - but all the EEPROM are for US. you posted some screenshots of the original tplink-firmware for Israel: they made nearly everything wrong for the user. bye, bastian. _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
