All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gertjan van Wingerde <gwingerde@kpnplanet.nl>
To: mcgrof@gmail.com
Cc: linux-wireless@vger.kernel.org
Subject: Regulatory Framework & rt2x00.
Date: Thu, 02 Oct 2008 22:20:23 +0200	[thread overview]
Message-ID: <48E52D07.8050900@kpnplanet.nl> (raw)

Hi Luis,

I'm working on making rt2x00 use the regulatory framework to report its 
EEPROM region settings to mac80211, and I have stumbled upon an issue 
that I don't really know how to solve with the current regulatory 
framework code.

The problem I'm facing is that many of the Ralink devices have 2 region 
settings in their EEPROM, one for 802.11a networks, and one for 
802.11[bgn] networks. So far I have only seen devices where these two 
settings contain the same region indication, but I don't know whether 
this is the case for all devices.

At this point in time I use the regulatory_hint function at driver 
start-up time to communicate the region setting that matches the 
configured band, but that would (probably) not hold up when the user 
reconfigures the mode.

So, at this point in time I have the following questions:
1. How would I be able to communicate both these settings to the 
regulatory framework?
2. Should I re-use regulator_hint whenever the configured band changes?
3. Would a driver supplied region override a user configured setting 
(via iw/crda)?

I would appreciate your help in solving this issue.

---
Gertjan van Wingerde
rt2x00 project developer
http://rt2x00.serialmonkey.com/

             reply	other threads:[~2008-10-02 20:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-02 20:20 Gertjan van Wingerde [this message]
2008-10-02 19:33 ` Regulatory Framework & rt2x00 Luis R. Rodriguez
2008-10-03 20:20   ` Gertjan van Wingerde
2008-10-03 14:32     ` Luis R. Rodriguez
2008-10-03 22:19       ` Gertjan van Wingerde
2008-10-03 15:45         ` Luis R. Rodriguez
2008-10-03  8:05 ` Johannes Berg
2008-10-03 18:18   ` Ivo van Doorn
2008-10-03 20:02     ` Gertjan van Wingerde
2008-10-03 13:14       ` Luis R. Rodriguez

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=48E52D07.8050900@kpnplanet.nl \
    --to=gwingerde@kpnplanet.nl \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    /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.