On Fri, May 29, 2009 at 10:55 AM, Luis R. Rodriguez <lrodrig...@atheros.com> wrote: > On Fri, May 29, 2009 at 05:26:51AM -0700, Bob Copeland wrote:
>> Anyway, I don't care too strongly about it, but it seems Atheros use >> world roaming so much that the eeprom value is often meaningless. > > Most of the cards I've used or tested are for the US actually. > > Either way -- Atheros is not the only vendor which abides by this, > try to look at the big picture. This is more of an architectural design > question > on the Atheros cards in consideration for regulatory compliance. If regulatory > laws made it clear that trusting the user blindly is 100% possible I think > you would have seen this embraced by many vendors, its just not the case > today and its actually is one motivation for some vendors to not open up > their drivers under fear uncertainty and doubt. BTW I should note that CRDA and wireless-regdb is also designed to allow for vendor customers (whoever is packing the chipsets) to provide customized regulatory.bin files and sign by them. This would allow companies like Ubiquity, for example, to sign away a regulatory.bin for a customer that is legally able to use high EIRP. In the case for Atheros cards it means the EEPROM needs to be programmed specifically for a country regulatory domain, and definitely not world roaming. An example of specialized cards here could be the Public Safety SKU. Whoever sells these cards can customize the database for their customers as they see fit. This would allow the cards to use new regulatory rules without modifying the driver at all. Luis _______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
