linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: Gertjan van Wingerde <gwingerde@kpnplanet.nl>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	mcgrof@gmail.com, linux-wireless@vger.kernel.org
Subject: Re: Regulatory Framework & rt2x00.
Date: Fri, 3 Oct 2008 20:18:24 +0200	[thread overview]
Message-ID: <200810032018.24910.IvDoorn@gmail.com> (raw)
In-Reply-To: <1223021104.24551.61.camel@johannes.berg>

Hi,

> > 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.
> 
> I think you basically have two choices depending on whether you have a
> country code in the eeprom or not.
> 
> If you have a country code, I suggest you just use either one.
> 
> As far as I know, though, you don't have country codes. So if there's a
> valid code in the EEPROM you probably should use the regdomain struct
> hint rather than the alpha2 hint and build a regdomain that contains
> both 2.4 and 5 GHz channels based on the two region values you have.

For rt61pci and rt73usb you should do as Johannes suggested by using the
regdomain struct. For rt2500pci and rt2500usb it sounds much easier to
take the country code from the EEPROM since those devices only contain
a single regdom value.

Ivo

  reply	other threads:[~2008-10-03 18:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-02 20:20 Regulatory Framework & rt2x00 Gertjan van Wingerde
2008-10-02 19:33 ` 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 [this message]
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=200810032018.24910.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=gwingerde@kpnplanet.nl \
    --cc=johannes@sipsolutions.net \
    --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 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).