linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: wireless <linux-wireless@vger.kernel.org>
Subject: Questions about mac80211 settings
Date: Sun, 05 Aug 2007 17:59:40 -0500	[thread overview]
Message-ID: <46B6565C.2050008@lwfinger.net> (raw)

In net/mac80211/regdomain.c, the following structure and data values are entered:

struct ieee80211_channel_range {
         short start_freq;
         short end_freq;
         unsigned char power_level;
         unsigned char antenna_max;
};

static const struct ieee80211_channel_range ieee80211_fcc_channels[] = {
         { 2412, 2462, 27, 6 } /* IEEE 802.11b/g, channels 1..11 */,
         { 5180, 5240, 17, 6 } /* IEEE 802.11a, channels 36..48 */,
         { 5260, 5320, 23, 6 } /* IEEE 802.11a, channels 52..64 */,
         { 5745, 5825, 30, 6 } /* IEEE 802.11a, channels 149..165, outdoor */,
         { 0 }
};

Is the "power_level" here supposed to be the power setting in dBm? If so, where do these numbers 
come from? The FCC regulations call for 20 dBm for the 2.4 GHz band, and 23, 30, and 36 dBm for the 
3 A bands.

The driver passes a set of channels, power levels and antenna values in the call to 
ieee80211_register_hwmode. These power settings seem to be discarded. Why? Shouldn't they overwrite 
the values defined above?

These power settings are of interest because driving the BCM4311 device at its maximum of 18.5 dBm 
severly cuts the performance at high data rates with the AP nearby. It probably causes distortion of 
the output.

Larry


Larry

                 reply	other threads:[~2007-08-05 22:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=46B6565C.2050008@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=linux-wireless@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).