linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gertjan van Wingerde <gwingerde@kpnplanet.nl>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: "Luis R. Rodriguez" <lrodriguez@atheros.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, 06 Jan 2009 23:06:51 +0100	[thread overview]
Message-ID: <4963D5FB.60409@kpnplanet.nl> (raw)
In-Reply-To: <200901062252.15677.IvDoorn@gmail.com>

On 01/06/09 22:52, Ivo van Doorn 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.
>>>
>>>        
>> OK. But the EEPROM definitions I got from Ralink on the Country
>> information indicate that there is only a single indication in the EEPROM.
>>      
>
> That is right, like I said the comments already indicates there the legacy code didn't contain the
> definitions (yet). ;)
>
>    
>>> GertJan, some comments about your patch:
>>>
>>>
>>>        
>>>> diff --git a/drivers/net/wireless/rt2x00/rt2400pci.h b/drivers/net/wireless/rt2x00/rt2400pci.h
>>>> index 9aefda4..986e428 100644
>>>> --- a/drivers/net/wireless/rt2x00/rt2400pci.h
>>>> +++ b/drivers/net/wireless/rt2x00/rt2400pci.h
>>>> @@ -806,6 +806,13 @@
>>>>    #define EEPROM_TXPOWER_2		FIELD16(0xff00)
>>>>
>>>>    /*
>>>> + * EEPROM geography.
>>>> + * GEO: Default geography setting for device.
>>>> + */
>>>> +#define EEPROM_GEOGRAPHY		0x17
>>>> +#define EEPROM_GEOGRAPHY_GEO		FIELD16(0xff00)
>>>>
>>>>          
>>> Where did you find this definition? I couldn't find it in the legacy driver or the specsheets.
>>>
>>>        
>> I got an excerpt from the EEPROM definition for the rt2460 chip (which I
>> received with the help of Luis). It's defined in there.
>>      
>
> I assume you mean the file RT2460_DS_P1.3.pdf, could you point me to the right pagenumber?
>
>    
No, I meant RT2460_EEPROM_Channels.pdf, which was sent by Ralink a 
couple of months ago. You were copied on the email; let me know if you 
can't find them. Note that these were only small excerpts from the 
entire EEPROM definitions, only the parts on geography information.

---
Gertjan.

  reply	other threads:[~2009-01-06 22:06 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
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 [this message]
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=4963D5FB.60409@kpnplanet.nl \
    --to=gwingerde@kpnplanet.nl \
    --cc=ivdoorn@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=lrodriguez@atheros.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).