On Wed, Apr 6, 2011 at 5:23 AM, Christian Lamparter
<chunkeey@xxxxxxxxxxxxxx> wrote:
> On Wednesday 06 April 2011 05:26:28 Joe Culler wrote:
>> [...]
>> I have a problem with carl9170 driver with my d-link dwa-160 under
>> linux-2.6.39-rc1.
>> Here's the dmesg:
>
>> [ 3114.257063] ath: EEPROM regdomain: 0x5c
>> [ 3114.257066] ath: EEPROM indicates we should expect a direct regpair map
>> [ 3114.257069] ath: invalid regulatory domain/country code 0x5c
>> [ 3114.257071] ath: Invalid EEPROM contents
> clearly, the regdomain code 0x5c is not defined in the
> drivers/net/wireless/ath/regd_common.h => regDomainPairs struct.
>
> this would be easy to fix [see attached patch], however I'm
> not quite sure what to do about the 5GHz band in this case,
> since the CTL_FCC is more restrictive than it should be.
>
> Regards,
> Â Â Â ÂChr
>
> ---
> diff --git a/drivers/net/wireless/ath/regd_common.h b/drivers/net/wireless/ath/regd_common.h
> index 248c670..5c2cfe6 100644
> --- a/drivers/net/wireless/ath/regd_common.h
> +++ b/drivers/net/wireless/ath/regd_common.h
> @@ -195,6 +195,7 @@ static struct reg_dmn_pair_mapping regDomainPairs[] = {
> Â Â Â Â{APL9_WORLD, CTL_ETSI, CTL_ETSI},
>
> Â Â Â Â{APL3_FCCA, CTL_FCC, CTL_FCC},
> + Â Â Â {APL7_FCCA, CTL_FCC, CTL_FCC},
> Â Â Â Â{APL1_ETSIC, CTL_FCC, CTL_ETSI},
> Â Â Â Â{APL2_ETSIC, CTL_FCC, CTL_ETSI},
> Â Â Â Â{APL2_APLD, CTL_FCC, NO_CTL},
I verified internally with our other code and this is correct, APL7
maps to FCC CTL and FCCA maps to FCC CTL as well. For an upstream
patch:
Acked-by: Luis R. Rodriguez <lrodriguez@xxxxxxxxxxx>
Luis
--
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
