Hi All,
I used to run one of "THE" compliance labs....
Who really cares about compliance ??!! The real question is does it work, does it *REALLY* work !! Can you reset it reliably? Can you debug it?
I too ONLY consider open source as even worth spending my time with.
The original Atheros driver for MITs roofnet was 50% of the size of their "regular" OEM driver. And it worked pretty well !! Pretty telling. AFAIK the MIT sources were never leaked to the web?
I keep thinking someone *SHOULD* do a WIFI interface to ethernet with an open radio and and open VHDL fpga design. That way we could all see what was *REALLY* happending with the RF ! MUCH better than ANY analyser out there.
And it would just get better and become more reliable over time.
Hurrah for open source!
Wiz
On Tue, 4 May 2010, elektra wrote:
Hi Franz -
there are certified devices out there, running OpenWrt / open-source drivers. May I ask, what particular regulator issues you have in mind, that a open- source driver can not comply with? Read: Are you sure you don't get the regulators blessing for your product with a open-source driver?
Besides: Do you know this song by Eric Idle, regarding the FCC?
http://www.youtube.com/watch?v=F4ajZ-5kTXk
A few memes:
Any product can be tampered with.
In many certified devices you can simply switch the reg domain. Then choose Japan, for example. Now you can transmit on channel 14 in the 2.4GHz range. Not so legal anywhere outside of Nippon.
The old Broadcom chipset / proprietary driver can be configured to transmit at 250mW with the proprietary closed source driver. Hence you can transmit at ~25dbm EIRP (with the stock antennas), far beyond the ETSI regulations of 20dBm EIRP.
Any device with a external antenna connector can be used together with a high- gain antenna. Again you get far beyond the legal limits.
Cheers, Elektra