MadWifi developers move to ath5k
Posted Sep 21, 2007 19:19 UTC (Fri) by alan_carr
Parent article: MadWifi developers move to ath5k
One of the things that has bothered me is the whole mess with the FCC's declaration of requiring security through obscurity (closed source). I mean, someone is going to bring up this FUD where can you even ship a driver that has access to radio parameters... hopefully in the documentation somewhere they state things like parameters controller RF pieces are for the most part restricted to the user (channel selection being the exception).
I used to work for a company doing GSM basestation design, and even *code releases* that had anything to do with the radio/baseband layer had to be approved again by the regulatory agency before release. Of course, a lot of this is to generate a cash cow, but of course it pretty much guarantees compliance and interoperability.
I just wonder how Dell will ship a laptop with an open WLAN driver with the FCC as it is today. What's worse is that the FCC sets no clear boundary for dividing where controls are and what exactly they need to be. Just that they ruled the user shouldn't be able to modify these settings. I mean, somebody could reverse assemble the binary driver and make hacks technically... so where do you draw the damn line... oh well... /vent off :D
to post comments)