"Luis R. Rodriguez" <mcgrof@xxxxxxxxx> writes: >> Software (the official Atheros driver, to be precise) says 0 isn't >> exactly US. >> Hardware (card) manufacturer says 0 isn't US. > > Would it make you happy if I send a patch to clarify that? That would fix a good part of the problem, yes. TIA. > I've indicated that your card is already working as it was designed. But that's not the case. The Atheros _chips_ are probably working as designed. The card(s) does not, since it was designed for European market, and its designer confirms this. Yet, by default, this card (+ driver) enables channels which should be disabled in Europe, and disables others, which should be available. This is caused by interaction between two pieces - the driver and the card. Most probably each one of them, alone, is not at fault. > The EEPROM is not something that was designed for end users to modify. Though I'm not end user, I will leave it for others to modify, no problem. I only need a proof (such as the driver printing "US") it should be modified. > Who programmed your EEPROM choose that for a reason, and only they and > as per Atheros's documentation would know what the goal was, and those who were told about it. The stated goal is known, and I assume the calibration data is available as well (I don't have these cards physically ATM). > If you want to muck with the EEPROM/code for regulatory compliance > that is up to you and that is simply not supported due to a few > things. One of them is calibration data which may or not be available > for the region you would choose blindly. Properly enabling users to > change their regulatory domain at their own whim really requires more > involvement, sure you'd be able to use some additional channels but it > by no means would mean that they are in compliance or that the EIRP > you use hits the actual desired target. The important part really is > compliance. Precisely. To be compliant I have to restrict usage to a specific set of frequencies. Unfortunately it's a different set than the one in US. > The regulatory code on for the Atheros drivers enables usage only of > the channels dictated by the EEPROM and what we in software match that > EEPROM code to tables in software. This is by design. The Linux > regulatory framework allows you to further restrict the device further > but for Atheros cards if you change countries you will not get new > channels if your original programmed regulatory domain does not allow > for it. Yes, and it fits the needs nicely - if the card manufacturer's idea about meaning of the EEPROM matches the driver. -- Krzysztof Halasa -- 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
