All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: "Luis R. Rodriguez" <mcgrof@frijolero.org>
Cc: <ath6kl-devel@qualcomm.com>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 2/2] ath6kl: add support for changing contry code
Date: Thu, 19 Jul 2012 14:11:28 +0300	[thread overview]
Message-ID: <5007EB60.60705@qca.qualcomm.com> (raw)
In-Reply-To: <CAB=NE6WjW-f=giqEEycNcZqjjB7SuioiMyEbrLcGaz8oD1CPNA@mail.gmail.com>

On 07/12/2012 10:40 PM, Luis R. Rodriguez wrote:
> On Thu, Jul 12, 2012 at 2:39 AM, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
>> +config ATH6KL_REGDOMAIN
>> +       bool "Atheros ath6kl regdomain support"
>> +       depends on ATH6KL
>> +       depends on CFG80211_CERTIFICATION_ONUS
>> +       ---help---
>> +         Enabling this makes it possible to change the regdomain in
>> +         the firmware. This can be only enabled if regulatory requirements
>> +         are taken into account.
> 
> You will need to add wiphy->features |=
> NL80211_FEATURE_CELL_BASE_REG_HINTS in order to enable the base
> station hints to propagate to the driver and even to the core,
> otherwise this is ignored. This was addressed starting at v4 of my
> onus patches. Given this, I think it makes sense to rename the option
> to enable / disable base station hints and to update the language to
> clearly reflect that is the only type of hint that would be used to
> update the firmware regulatory domain.

I was planning to do this in two phases, first do a simple
implementation (these two patches) and then add support for the cellular
BTS hints.

Kalle

      reply	other threads:[~2012-07-19 11:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-12  9:39 [PATCH 1/2] ath6kl: refactor wmi scan command Kalle Valo
2012-07-12  9:39 ` [PATCH 2/2] ath6kl: add support for changing contry code Kalle Valo
2012-07-12 19:40   ` Luis R. Rodriguez
2012-07-19 11:11     ` Kalle Valo [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=5007EB60.60705@qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath6kl-devel@qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@frijolero.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.