From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Gertjan van Wingerde <gwingerde@kpnplanet.nl>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
Ivo van Doorn <ivdoorn@gmail.com>,
"John W. Linville" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"rt2400-devel@lists.sourceforge.net"
<rt2400-devel@lists.sourceforge.net>
Subject: Re: [PATCH] rt2x00: Provide regulatory hint with rt2500pci/usb
Date: Tue, 6 Jan 2009 12:47:44 -0800 [thread overview]
Message-ID: <20090106204744.GB21980@tesla> (raw)
In-Reply-To: <4963BFEF.2090006@kpnplanet.nl>
On Tue, Jan 06, 2009 at 12:32:47PM -0800, Gertjan van Wingerde wrote:
> On 01/06/09 00:45, Luis R. Rodriguez wrote:
> > On Mon, Jan 05, 2009 at 02:21:46PM -0800, Ivo van Doorn wrote:
> >
> >> On Monday 05 January 2009, Gertjan van Wingerde wrote:
> >>
> >>> On 01/05/09 21:08, Luis R. Rodriguez wrote:
> >>>
> >>> The problem isn't there for the bits that Ivo sent, as the rt2500 devices don't support the a band.
> >>>
> >> For rt2500pci and rt2500usb there are chipsets which support 5GHz (they are rare, but they do exist),
> >> comments for the Ralink drivers indicate they simply didn't add the regulatory domain definitions yet.
> >>
> >
> > Based on the documentation from the EEPROM for all devices I read that its recommended
> > that the EEPROM *not be relied on for the regulatory domain*, instead it recommends the
> > windows registry be used.
> >
> > Based on tests for the devices with only one band, do are you seeing an actual regulatory
> > domain in the EEPROM?
> >
> > To deal with the issue of having two separate EEPROM values for a regulatory domain
> > and since the documentation indicates to not rely on it I would advise to allow users
> > to be compliant by selecting the country they are in. wpa_supplicant has support for
> > selecting country now, and so does iw. Eventually I see Network Manager letting users
> > select the country. But you guys are the maintainers and developers so you will know
> > better.
> >
>
> My tests indicate that there are devices out there that have this
> information set in the EEPROM. Based on tests with my own patch, and my
> own devices, I have been able to determine the following:
>
> 1. rt2400pci --> don't know, don't own a rt2400pci device.
> 2. rt2500pci --> don't know, don't own a rt2500pci device anymore.
> 3. rt2500usb --> my e-tech device (not sure which type; the device
> doesn't say it) has an actual domain set for the bg band.
> 4. rt61pci --> my Sitecom WL151 device does not contain actual domain
> information.
> 5. rt73usb --> my Sitecom WL113-002 device does contain actual domain
> information, and the codes for the bg band and a band are the same.
> 6. rt2800pci --> my Sitecom WL182 device does contain actual domain
> information, and the codes for the bg band and a band are the same.
> 7. rt2800usb --> my Sitecom WL181 device does contain actual domain
> information, and the codes for the bg band and a band are the same.
>
> So, there are devices out there that do contain "meaningful" regulatory
> information.
>
> Luis, the definitions for the a-band EEPROM codes only give the channel
> numbers, it doesn't indicate a real "country". Is there any way we can
> check whether these sets of channels are actually consistent with the
> regulations of specific countries?
You can help contribute to the wireless-regdb and check that the valid
channels apply there.
Luis
next prev parent reply other threads:[~2009-01-06 20:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-04 19:21 [PATCH] rt2x00: Provide regulatory hint with rt2500pci/usb Ivo van Doorn
2009-01-05 20:08 ` Luis R. Rodriguez
2009-01-05 21:29 ` Gertjan van Wingerde
2009-01-05 22:21 ` Ivo van Doorn
2009-01-05 23:45 ` Luis R. Rodriguez
2009-01-06 17:32 ` Ivo van Doorn
2009-01-06 17:36 ` Luis R. Rodriguez
2009-01-06 17:47 ` Ivo van Doorn
2009-01-06 20:39 ` Gertjan van Wingerde
2009-01-06 20:49 ` Luis R. Rodriguez
2009-01-06 21:51 ` Ivo van Doorn
2009-01-06 22:11 ` Gertjan van Wingerde
2009-01-13 22:07 ` Luis R. Rodriguez
2009-01-06 20:32 ` Gertjan van Wingerde
2009-01-06 20:47 ` Luis R. Rodriguez [this message]
2009-01-06 22:15 ` Gertjan van Wingerde
2009-01-06 22:23 ` Luis R. Rodriguez
2009-01-06 22:50 ` Gertjan van Wingerde
2009-01-06 20:17 ` Gertjan van Wingerde
2009-01-06 21:52 ` Ivo van Doorn
2009-01-06 22:06 ` Gertjan van Wingerde
2009-01-06 22:12 ` Ivo van Doorn
2009-01-06 22:17 ` 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=20090106204744.GB21980@tesla \
--to=lrodriguez@atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=gwingerde@kpnplanet.nl \
--cc=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rt2400-devel@lists.sourceforge.net \
/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).