linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Young <dyoung@pobox.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Pavel Roskin <proski@gnu.org>,
	linux-wireless@vger.kernel.org,
	Scott Raynel <scottraynel@gmail.com>,
	radiotap@mail.ojctech.com
Subject: Re: RFC: radiotap discrepancy in Linux vs OpenBSD
Date: Mon, 26 Mar 2007 11:59:08 -0500	[thread overview]
Message-ID: <20070326165908.GK31621@che.ojctech.com> (raw)
In-Reply-To: <43e72e890703260841v56047559y90b7c25c9c458564@mail.gmail.com>

On Mon, Mar 26, 2007 at 11:41:38AM -0400, Luis R. Rodriguez wrote:
> CC'ing radiotap list, this time with your comments inline.
> 
> On 3/25/07, David Young <dyoung@pobox.com> wrote:
> >On Sun, Mar 25, 2007 at 11:24:16PM -0400, Pavel Roskin wrote:
> >> Hello!
> >
> >(Oops, this time cc'd radiotap.)
> >
> >The place to discuss this is the mailing list
> >radiotap@ojctech.com, which I have cc'd.  Subscribe at
> ><http://mail.ojctech.com/mailman/listinfo/radiotap>.  Please feel free
> >to circulate the URL.
> >
> >> I have noticed two different incompatible changes to enum
> >> ieee80211_radiotap_type in ieee80211_radiotap.h.
> >>
> >> One is found in the current wireless-2.6.git:
> >>
> >>         IEEE80211_RADIOTAP_RX_FLAGS = 14,
> >>         IEEE80211_RADIOTAP_TX_FLAGS = 15,
> >>         IEEE80211_RADIOTAP_RTS_RETRIES = 16,
> >>         IEEE80211_RADIOTAP_DATA_RETRIES = 17,
> >
> >These fields are slated to become part of the standard, I just haven't got
> >around to updating the manual page, yet.  I have time to do that tonight.
> >
> >> It was added together with Marvell Libertas USB driver.
> >
> >> Another set of the flags can be found in CVS OpenBSD:
> >>
> >>         IEEE80211_RADIOTAP_FCS = 14,
> >>         IEEE80211_RADIOTAP_HWQUEUE = 15,
> >>         IEEE80211_RADIOTAP_RSSI = 16,
> >
> >These fields are not part of the standard, and they will not become part
> >of the standard with these numbers.  This is the first time I have ever
> >heard of HWQUEUE and RSSI, actually.  What are they for?
> 
> RSSI is Received Signal Strength Indication. Its a measurement of the
> received radio signal strength. Unfortunately though RSSI units used
> are arbitrary and the maximum value differs amongst chipsets. From
> wikipedia:
> 
> --
> RSSI measurements will vary from 0 to 255 depending on the vendor. It
> consists of a one byte integer value. A value of 1 will indicate the
> minimum signal strength detectable by the wireless card, while 0
> indicates no signal. The value has a maximum of RSSI_Max. For example,
> Cisco Systems cards will return a RSSI of 0 to 100. In this case, the
> RSSI_Max is 100. The Cisco card can report 101 distinct power levels.
> Another popular Wi-Fi chipset is made by Atheros. An Atheros based
> card will return a RSSI value of 0 to 60.
> --
> 
> As Samuel Barber had recommended before, we should probably instead
> adopt RCPI. Quoting from his e-mail:

RCPI sounds desirable.  Let us avoid labeling a field RCPI if it isn't.
We may need both fields, RSSI (defined: uncalibrated, unsigned, unitless
signal strength, greater numbers -> greater strength) and RCPI (defined
per 802.11k draft 5.0).

Is 802.11k changing very rapidly, esp. the RCPI definition?

Dave

-- 
David Young             OJC Technologies
dyoung@ojctech.com      Urbana, IL * (217) 278-3933

      reply	other threads:[~2007-03-26 16:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-26  3:24 RFC: radiotap discrepancy in Linux vs OpenBSD Pavel Roskin
2007-03-26  3:37 ` David Young
2007-03-26 22:45   ` Pavel Roskin
2007-03-28 18:04     ` [Radiotap] " Marcelo Tosatti
2007-03-28 20:33       ` Pavel Roskin
2007-03-26  3:38 ` David Young
2007-03-26 15:41   ` Luis R. Rodriguez
2007-03-26 16:59     ` David Young [this message]

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=20070326165908.GK31621@che.ojctech.com \
    --to=dyoung@pobox.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    --cc=proski@gnu.org \
    --cc=radiotap@mail.ojctech.com \
    --cc=scottraynel@gmail.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 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).