On Mon, Nov 24, 2008 at 05:42:00PM -0800, Richard Farina wrote:
> Luis R. Rodriguez wrote:
> > On Mon, Nov 24, 2008 at 3:18 PM, Richard Farina <sidhayn@xxxxxxxxx> 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.
CRDA only speaks Part 15 rules for FCC as its only used for
802.11 right now. Feel free to expand it to use other stuff
but we also need to ensure it keeps working as it was and
there will also need to be a good use case for it to be merged.
> 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.
DSSS is used for 802.11b and pre 802.11b only, covered under
IEEE-802.11-2007 section 15 and are for rates 1Mbit/s and 2Mbit/s.
> The hardware handles this for us I think, that or somewhere deep dark
> and scary that I've never seen in the driver.
Since this is 802.11{FOO} related we need not care about it as yes, it
is hardware specific.
> Additionally .11a
> provides three different transmit power levels based on the frequency
> band you are in (and the use case).
CRDA is band agnostic on purpose -- originally I started with UNII band
notion stuff but that got pretty silly quickly. Johannes also knocked
some good sense into me.
What we have now allows us human creatures to assign name values to
whatever bands we want at any point in time and not worry about
what name they fall under, and it still works. This makes it more
FCC agnostic, which became a very important requirement. So please
consider *all* regulatory agencies when thinking about the overall
design of CRDA.
> What I would need this additional
> feature for is licensed use
User your own custom database and CRDA! That's one of the reasons
why it was ISC licensed. Go do what you like with your own db (including
using sharks with lasers on their head).
> but I'm sure that somewhere in the world,
> someone has a unlicensed limitation such that would make this relevant.
When you do find concrete evidence, instead of speculating, please do
submit a patch and document your findings.
> 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.
CRDA allows for custom solutions, if you know what you are doing
and have a license for it, go wild.
> 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 :-)
Please only bother with sending patches which work for unlicensed
communication devices usage only.
Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
