> So it seems like your three options translate to: > 1. full Open Source: happy Open Source developers (+), can't > sell device (big -) > 2. firmware RF code: happy FOSS ppl (+), can sell device > (+), depends on chip design...(not always > possible) > 3. RF blob: mad FOSS ppl (- but can live with if no other > option), can sell device(+) If your device really doesn't have a firmware (some claim firmware is necessary to ensure real-time properties of the protocol) then you could also do: 4. write the driver for Windows in the usual, close source form, "leak" or give docs to some Linux developers and let they write the driver for the device. FCC can't object, you didn't wrote the driver :-) Chances are actually quite high that the Linux people write a better driver than you :-) Did you know about Greg Kroah-Hahn's "driver for free" incentive? http://www.kroah.com/log/linux/free_drivers.html - 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
