linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Farina <sidhayn@gmail.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: John Linville <linville@tuxdriver.com>,
	wireless <linux-wireless@vger.kernel.org>,
	Michael Green <Michael.Green@atheros.com>
Subject: Re: wireless-regdb: update regulatory rules for US 2.3-2.4GHz and 5.65-5.925GHz
Date: Mon, 24 Nov 2008 20:42:00 -0500	[thread overview]
Message-ID: <492B57E8.2010101@gmail.com> (raw)
In-Reply-To: <43e72e890811241530t44245e4ar3fd5797afcc451c0@mail.gmail.com>

Luis R. Rodriguez wrote:
> On Mon, Nov 24, 2008 at 3:18 PM, Richard Farina <sidhayn@gmail.com> wrote:
>   
>> Luis R. Rodriguez wrote:
>>     
>>> On Mon, Nov 24, 2008 at 02:43:19PM -0800, Richard Farina wrote:
>>>
>>>       
>>>> The above frequencies are allowed by FCC part 97 to amateur radio
>>>> operator as primary use, this doesn't even cover the secondary and
>>>> tertiary uses, just where amateurs are primary.
>>>>
>>>>         
>>> NACK -- For the US we use the wireless regulatory database for Part 15
>>> rules with 802.11 in mind.
>>>
>>>
>>>       
>> Not only do I understand your reasoning, but I also agree.  Please do
>> consider the following (from that same email):
>>     
>
> Thanks :)
>
>   
>> This also introduces a new issue in crda of setting not only power limits
>> but power limits based on modulation.  It is permitted to use DSSS up to 100
>> watts, however, OFDM is permitted up to 1500 watts.
>>
>> Would it be an unreasonable request to have crda support modulation
>> restrictions and power limit based on modulation restrictions?
>>     
>
> This is odd, first time I hear about such a thing. Do you have a
> pointer to Part 15 rules which clarifies this?
>
>   
Again, I'm only familiar with FCC regulations but I don't believe this 
is required for Part 15.  The IEEE802.11 rules do allow for some odd 
stuff but the really odd stuff tends to be handled in hardware.  For 
instance, we can only use OFDM on the 5GHz bands, no DSSS is permitted.  
The hardware handles this for us I think, that or somewhere deep dark 
and scary that I've never seen in the driver.  Additionally .11a 
provides three different transmit power levels based on the frequency 
band you are in (and the use case).  What I would need this additional 
feature for is licensed use but I'm sure that somewhere in the world, 
someone has a unlicensed limitation such that would make this relevant.  
I suppose we can all wait around until I can successfully google such a 
case or someone with relevant first hand experience comes along, but 
frankly, if it isn't that painful to do it would allow the licensed 
users a much greater flexibility to use the hardware without 
accidentally breaking the law.  Please consider it a request without 
official requirement, if someone is bored, great, otherwise I'll either 
learn to code better or find someone who is bored :-)

thanks,
Rick Farina

>   Luis
>
>   


  reply	other threads:[~2008-11-25  1:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-24 22:43 wireless-regdb: update regulatory rules for US 2.3-2.4GHz and 5.65-5.925GHz Richard Farina
2008-11-24 23:04 ` Luis R. Rodriguez
2008-11-24 23:18   ` Richard Farina
2008-11-24 23:30     ` Luis R. Rodriguez
2008-11-25  1:42       ` Richard Farina [this message]
2008-11-26  0:47         ` 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=492B57E8.2010101@gmail.com \
    --to=sidhayn@gmail.com \
    --cc=Michael.Green@atheros.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=lrodriguez@atheros.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).