On Tue, Feb 12, 2008 at 10:45:40AM +0200, Budhee Jamaich wrote: > First - thank you for the detailed response! Yes, thanks Dan! > So even if a vendor is willng to completely Open Source it's code, > having FCC troubles > is a serious problem. The answer of course is "it depends". For example, depending on the device it might be possible to provide code to configure the device in "good" ways without necessarily revealing how to configure it in "bad" ways...YMMV. This may be more or less difficult depending on the exact details of your hardware design. > Is there any vendor who walked this path ? complete Open Source RF code ? > If yes, has it's chip got FCC certified ? The rtl8180 driver does not use any firmware and is completely open source. The driver code contains lots of "magic number" tables related to initializing and configuring the device. I don't know enough about the hardware to tell you if the hardware is flexible enough to be easily forced into non-compliant power or frequency settings, so I can't really characterize the risk to Realtek. I do know that Realtek supported rtl8180 driver development with datasheets and access to developers. Presumably they feel that whatever risk there is is acceptable to their business. Hth! John -- John W. Linville linville@xxxxxxxxxxxxx - 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
