linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: John Williams <john@pond-weed.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] rtl8192cu driver ignores eeprom channel plan
Date: Mon, 05 Mar 2012 19:52:48 -0600	[thread overview]
Message-ID: <4F556DF0.3070806@lwfinger.net> (raw)
In-Reply-To: <20120305213956.7c383096@buffy.scoobygang>

On 03/05/2012 03:39 PM, John Williams wrote:
> Larry,
>
> The various rtl8192xx drivers read the manufacturer-set channel plan
> into efuse.eeprom_channelplan, but ignore this and use
> efuse.channel_plan (which is never initialized) when deciding which
> channels to allow. The patch below allowed my device, purchased in
> Europe, to see channels 12 and 13 when configured with "iw reg set EC"
>
> It needs more work in order to accept being configured for arbitrary countries: would you like me to work on a more comprehensive patch?

Please - I have plenty to do. I had never had any problems with the allowed 
channels, as I use CRDA and it sets my domain to US, which is as restrictive as any.

I just tested, and the RTL8192CE that I have installed at the moment has 0xA 
(COUNTRY_CODE_WORLD_WIDE_13) in the eeprom, which happens to be what is set in 
rtlpriv->efuse.channel_plan in rtl8192ce. That is not surprising as the card 
came from Realtek and I would expect something appropriate for China.

Larry

      reply	other threads:[~2012-03-06  1:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-05 21:39 [PATCH] rtl8192cu driver ignores eeprom channel plan John Williams
2012-03-06  1:52 ` Larry Finger [this message]

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=4F556DF0.3070806@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=john@pond-weed.com \
    --cc=linux-wireless@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).