2011/1/19 Bruno Randolf <br1@xxxxxxxxxxx>: > They are unused in ath5k and a more detailled definition is in > ath/regd_common.h. > > Signed-off-by: Bruno Randolf <br1@xxxxxxxxxxx> > --- > Âdrivers/net/wireless/ath/ath5k/eeprom.h |  23 ----------------------- > Â1 files changed, 0 insertions(+), 23 deletions(-) > > diff --git a/drivers/net/wireless/ath/ath5k/eeprom.h b/drivers/net/wireless/ath/ath5k/eeprom.h > index d46f105..6511c27 100644 > --- a/drivers/net/wireless/ath/ath5k/eeprom.h > +++ b/drivers/net/wireless/ath/ath5k/eeprom.h > @@ -268,29 +268,6 @@ enum ath5k_ctl_mode { >    ÂAR5K_CTL_MODE_M = 15, > Â}; > > -/* Default CTL ids for the 3 main reg domains. > - * Atheros only uses these by default but vendors > - * can have up to 32 different CTLs for different > - * scenarios. Note that theese values are ORed with > - * the mode id (above) so we can have up to 24 CTL > - * datasets out of these 3 main regdomains. That leaves > - * 8 ids that can be used by vendors and since 0x20 is > - * missing from HAL sources i guess this is the set of > - * custom CTLs vendors can use. */ > -#define    ÂAR5K_CTL_FCC  Â0x10 > -#define    ÂAR5K_CTL_CUSTOM 0x20 > -#define    ÂAR5K_CTL_ETSI  0x30 > -#define    ÂAR5K_CTL_MKK  Â0x40 > - > -/* Indicates a CTL with only mode set and > - * no reg domain mapping, such CTLs are used > - * for world roaming domains or simply when > - * a reg domain is not set */ > -#define    ÂAR5K_CTL_NO_REGDOMAIN  0xf0 > - > -/* Indicates an empty (invalid) CTL */ > -#define AR5K_CTL_NO_CTL        Â0xff > - > Â/* Per channel calibration data, used for power table setup */ > Âstruct ath5k_chan_pcal_info_rf5111 { >    Â/* Power levels in half dbm units > Acked-by: Nick Kossifidis <mickflemm@xxxxxxxxx> -- GPG ID: 0xD21DB2DB As you read this post global entropy rises. Have Fun ;-) Nick -- 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