netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: netdev@vger.kernel.org, John Linville <linville@tuxdriver.com>
Subject: [PATCH] Changes to ieee80211.h for user space regulatory daemon
Date: Tue, 30 May 2006 11:55:42 -0500	[thread overview]
Message-ID: <447C790E.1030702@lwfinger.net> (raw)

Attached are two small patches for include/net/ieee80211.h to prepare for later submission of code 
to implement a user-space daemon that supplies 802.11 regulatory information.

The first change adds a bit indicating that 802.11h rules are to be applied to a channel. As 
discussed earlier in this list, a single bit is unlikely to be sufficient; however, at this time I 
have been unable to find any regulations implementing differences between 802.11a and 802.11h other 
than DFS, radar detection and passive scanning. A single bit is thus sufficient to convey to the 
driver that these rules should be obeyed.

The second change adds comments to the freq and max_power fields of struct ieee80211_channel to 
indicate the units that are used.

Signed-Off-By: Larry Finger <Larry.Finger@lwfinger.net>

index 293e920..6a2f60c 100644
--- a/include/net/ieee80211.h
+++ b/include/net/ieee80211.h
@@ -968,6 +968,7 @@ #define IEEE80211_52GHZ_CHANNELS (IEEE80

  enum {
	IEEE80211_CH_PASSIVE_ONLY = (1 << 0),
+	IEEE80211_CH_80211H_RULES = (1 << 1),
	IEEE80211_CH_B_ONLY = (1 << 2),
	IEEE80211_CH_NO_IBSS = (1 << 3),
	IEEE80211_CH_UNIFORM_SPREADING = (1 << 4),
@@ -976,10 +977,10 @@ enum {
  };

  struct ieee80211_channel {
-	u32 freq;
+	u32 freq;	/* in MHz */
	u8 channel;
	u8 flags;
-	u8 max_power;
+	u8 max_power;	/* in dBm */
  };

  struct ieee80211_geo {

             reply	other threads:[~2006-05-30 16:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-30 16:55 Larry Finger [this message]
2006-06-05 18:59 ` [PATCH] Changes to ieee80211.h for user space regulatory daemon John W. Linville
2006-06-05 21:10   ` 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=447C790E.1030702@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.org \
    /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).