From: Kalle Valo <kvalo@codeaurora.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: devel@driverdev.osuosl.org, linux-wireless@vger.kernel.org,
Stable <stable@vger.kernel.org>
Subject: Re: [PATCH] rtlwifi: Fix missing country code for Great Britain
Date: Mon, 22 Aug 2016 18:36:59 +0300 [thread overview]
Message-ID: <87wpj8vmqs.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1471619674-29439-1-git-send-email-Larry.Finger@lwfinger.net> (Larry Finger's message of "Fri, 19 Aug 2016 10:14:34 -0500")
Larry Finger <Larry.Finger@lwfinger.net> writes:
> Some RTL8821AE devices sold in Great Britain have the country code of
> 0x25 encoded in their EEPROM. This value is not tested in the routine
> that establishes the regulatory info for the chip. The fix is to set
> this code to have the same capabilities as the EU countries.
>
> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
> Cc: Stable <stable@vger.kernel.org>
[...]
> --- a/drivers/net/wireless/realtek/rtlwifi/regd.c
> +++ b/drivers/net/wireless/realtek/rtlwifi/regd.c
> @@ -345,9 +345,9 @@ static const struct ieee80211_regdomain *_rtl_regdomain_select(
> return &rtl_regdom_no_midband;
> case COUNTRY_CODE_IC:
> return &rtl_regdom_11;
> - case COUNTRY_CODE_ETSI:
> case COUNTRY_CODE_TELEC_NETGEAR:
> return &rtl_regdom_60_64;
> + case COUNTRY_CODE_ETSI:
> case COUNTRY_CODE_SPAIN:
> case COUNTRY_CODE_FRANCE:
> case COUNTRY_CODE_ISRAEL:
I didn't check the full source, but here you seem to be changing also
the content of ETSI regdomain. The commit log doesn't mention anything
about that so I want to double check that this is really intentionally.
--
Kalle Valo
next prev parent reply other threads:[~2016-08-22 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 15:14 [PATCH] rtlwifi: Fix missing country code for Great Britain Larry Finger
2016-08-22 15:36 ` Kalle Valo [this message]
2016-08-22 19:23 ` Larry Finger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wpj8vmqs.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=Larry.Finger@lwfinger.net \
--cc=devel@driverdev.osuosl.org \
--cc=linux-wireless@vger.kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.