From: Larry Finger <Larry.Finger@lwfinger.net>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: devel@driverdev.osuosl.org, linux-wireless@vger.kernel.org,
littlesmartguy@gmail.com, gabe@codehaus.org,
Stable <stable@vger.kernel.org>
Subject: Re: [PATCH] rtlwifi: rtl8821ae: Fix 5G failure when EEPROM is incorrectly encoded
Date: Thu, 21 Jan 2016 02:56:39 -0600 [thread overview]
Message-ID: <56A09D47.6010600@lwfinger.net> (raw)
In-Reply-To: <87oacf1fho.fsf@kamboji.qca.qualcomm.com>
On 01/21/2016 02:52 AM, Kalle Valo wrote:
> Larry Finger <Larry.Finger@lwfinger.net> writes:
>
>> Recently, it has been reported that D-Link DWA-582 cards, which use an
>> RTL8812AE chip are not able to scan for 5G networks. The problems started
>> with kernel 4.2, which is the first version that had commit d10101a60372
>> ("rtlwifi: rtl8821ae: Fix problem with regulatory information"). With this
>> patch, the driver went from setting a default channel plan to using
>> the value derived from EEPROM.
>>
>> Bug reports at https://bugzilla.kernel.org/show_bug.cgi?id=111031 and
>> https://bugzilla.redhat.com/show_bug.cgi?id=1279653 are examples of this
>> problem.
>>
>> The problem was solved once I learned that the internal country code was
>> resulting in a regulatory set with only 2.4 GHz channels. With the RTL8821AE
>> chips available to me, the country code was such that both 2.4 and 5 GHz
>> channels are allowed. The fix is to allow both bands even when the EEPROM
>> is incorrectly encoded.
>>
>> Fixes: d10101a60372 ("rtlwifi: rtl8821ae: Fix problem with regulatory information")
>> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
>> Cc: littlesmartguy@gmail.com
>> Cc: gabe@codehaus.org
>> Cc: Stable <stable@vger.kernel.org> [v4.2+]
>
> I'll queue this to 4.5.
Thanks.
Larry
next prev parent reply other threads:[~2016-01-21 8:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 3:58 [PATCH] rtlwifi: rtl8821ae: Fix 5G failure when EEPROM is incorrectly encoded Larry Finger
2016-01-21 8:52 ` Kalle Valo
2016-01-21 8:56 ` Larry Finger [this message]
2016-01-25 13:22 ` Kalle Valo
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=56A09D47.6010600@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=devel@driverdev.osuosl.org \
--cc=gabe@codehaus.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=littlesmartguy@gmail.com \
--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.