Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: David Lamparter <lists@diac24.net>
Cc: Dan Williams <dcbw@redhat.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Jouni Malinen <j@w1.fi>
Subject: Re: [RFC] {cfg,nl}80211 API
Date: Wed, 13 Jun 2007 12:22:35 +0200	[thread overview]
Message-ID: <1181730155.29767.77.camel@johannes.berg> (raw)
In-Reply-To: <20070611230434.GA13221@charon.n2.diac24.net>

[-- Attachment #1: Type: text/plain, Size: 1572 bytes --]

Hi,

> - struct ieee80211_channel:
>   use (phymode, channel, 80211n-mode) as "key"; kill off frequency
>   (which will move to some get_channel_foobar function)

Hmm. Maybe we should've kept frequency. How do we want to handle
dot11ChannelStartingFactor (see 17.3.8.3.2 Channel numbering in
802.11j), I quote:

Change the text of 17.3.8.3.2 as follows:
Channel center frequencies are defined at every integral multiple of 5 MHz above Channel starting
frequency. The relationship between center frequency and channel number is given by Equation (27):

   Channel center frequency = Channel starting frequency + (nch × 5) (MHz)                      (27)

where
                              is 0,1,... 200,
   nch
   Channel starting frequency is defined as dot11ChannelStartingFactor × 500 kHz or
                              is defined as 5 GHz for systems where dot11RegulatoryClassesRequired is
                              false or not defined.
                              For example, dot11ChannelStartingFactor = 10 000 indicates that Channel
                              zero center frequency is 5.000 GHz. The value NULL for nch shall be
                              reserved, and a channel center frequency of 5.000 GHz shall be indicated by
                              dot11ChannelStartingFactor = 8000 and nch = 200. An SME managing
                              multiple channel sets can change the channel set being managed by changing
                              the value of dot11ChannelStartingFactor.


johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

  parent reply	other threads:[~2007-06-13 12:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-11 23:04 [RFC] {cfg,nl}80211 API David Lamparter
2007-06-12  9:15 ` Johannes Berg
2007-06-12 12:08   ` Dan Williams
2007-06-12 14:55     ` Tomas Winkler
2007-06-12  9:59 ` Holger Schurig
2007-06-12 13:15 ` David Lamparter
2007-06-12 13:58   ` Mark Powell
2007-06-12 16:45     ` Michael Wu
2007-06-12 17:01       ` Mark Powell
2007-06-13  6:46         ` Michael Wu
2007-06-13 13:25         ` David Lamparter
2007-06-13 16:08         ` Johannes Berg
2007-06-13 10:22 ` Johannes Berg [this message]
2007-06-13 13:18   ` [RFC] {cfg,nl}80211 API - 802.11j David Lamparter

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=1181730155.29767.77.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=dcbw@redhat.com \
    --cc=j@w1.fi \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lists@diac24.net \
    /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