From: Larry Finger <Larry.Finger@lwfinger.net>
To: Uli Kunitz <kune@deine-taler.de>,
netdev@vger.kernel.org, Faidon Liambotis <faidon@cube.gr>,
Rick Jones <rick.jones2@hp.com>,
Harald Welte <laforge@gnumonks.org>,
Jouni Malinen <jkm@devicescape.com>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [RFC] Proposed structure for Regulatory/Geographical Wireless database
Date: Fri, 05 May 2006 16:23:00 -0500 [thread overview]
Message-ID: <445BC234.4060909@lwfinger.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0605052256570.26787@p15091797.pureserver.info>
Uli Kunitz wrote:
> Larry Finger wrote:
>
>> * A new routine (ieee80211_init_geo ?) will be written to be called by the
>> driver to load the geo structure into the kernel. Information passed to the
>> daemon will be the country code in ASCII and whether the interface is to be
>> used indoors or outdoors.
>
> Would it be possible to support the regulatory domain codes as
> used in the outdated table 105 in Corrigendum 1 for 802.11b? The
> ZD1211 EEPROM contains only this code. An easy translation
> function would be sufficient. Maybe the group codes could be
> misused for it.
That certainly shouldn't be any difficulty. It could be done in the ZD1211 driver before it calls
the ieee80211_init_geo routine, or it could be done in the regulatory daemon. I assume that the
EEPROM contains X'10' for FCC regulations, X'31' for Spain, etc.
Larry
next prev parent reply other threads:[~2006-05-05 21:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 20:14 [RFC] Proposed structure for Regulatory/Geographical Wireless database Larry Finger
2006-05-05 21:08 ` Uli Kunitz
2006-05-05 21:23 ` Larry Finger [this message]
2006-05-06 5:07 ` Uli Kunitz
2006-05-05 21:10 ` Dan Williams
2006-05-05 21:52 ` Larry Finger
2006-05-06 1:31 ` Jouni Malinen
2006-05-07 2:02 ` Larry Finger
2006-05-06 18:48 ` Michael Buesch
2006-05-06 19:24 ` Larry Finger
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=445BC234.4060909@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=faidon@cube.gr \
--cc=hch@infradead.org \
--cc=jkm@devicescape.com \
--cc=kune@deine-taler.de \
--cc=laforge@gnumonks.org \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.