netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Simon Barber <simon@devicescape.com>
Cc: Dan Williams <dcbw@redhat.com>,
	netdev@vger.kernel.org, Jean Tourrilhes <jt@hpl.hp.com>
Subject: RE: proposal for new wireless configuration API
Date: Fri, 18 Aug 2006 09:01:47 +0200	[thread overview]
Message-ID: <1155884507.3425.5.camel@ux156> (raw)
In-Reply-To: <C86180A8C204554D8A3323D8F6B0A29F0165B02D@dhost002-46.dex002.intermedia.net>

On Thu, 2006-08-17 at 09:42 -0700, Simon Barber wrote:
> The spec for RSSI is very loose - RSSI is just a 8 bit unsigned number,
> guaranteed to be a monotonically increasing function of signal strength.
> You don't get to know anything about the scale, or linearity of the
> function. In essence RSSI is a vendor specific value, of no known units.
> Not very useful unless you know some card specific details to help
> interpret it.

Yeah, if you knew at least linearity it'd be more useful.

> Now some cards return a signal strength in dBm as the RSSI - note that
> this fits the requirements of a RSSI measure just fine. RCPI is simply a
                                  ^^^^
did you mean to write RCPI there?

> more tightly specified signal strength measure.

Ah, ok. Yes, I think we almost know how to make the bcm card report dBm
instead.

johannes

  parent reply	other threads:[~2006-08-18  7:02 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-15 15:28 proposal for new wireless configuration API Johannes Berg
2006-08-15 16:14 ` Luis R. Rodriguez
2006-08-16  7:26   ` Johannes Berg
2006-08-15 16:29 ` Dan Williams
2006-08-15 16:38   ` Michael Buesch
2006-08-15 18:14     ` Dan Williams
2006-08-15 19:13       ` Michael Buesch
2006-08-15 19:27         ` Simon Barber
2006-08-15 19:35           ` Michael Buesch
2006-08-15 20:06             ` Dan Williams
2006-08-15 19:59         ` Dan Williams
2006-08-16  7:14           ` Johannes Berg
2006-08-17 19:39         ` Jean Tourrilhes
2006-08-17 21:24           ` Michael Buesch
2006-08-17 23:29     ` Ulrich Kunitz
2006-08-18  7:12       ` Johannes Berg
2006-08-18 15:00         ` John W. Linville
2006-08-18 21:29         ` Ulrich Kunitz
2006-08-18 22:02           ` Michael Buesch
2006-08-21  7:31             ` Johannes Berg
2006-08-16  6:51   ` Johannes Berg
2006-08-16 18:02     ` Simon Barber
2006-08-17  7:19       ` Johannes Berg
2006-08-17 16:42         ` Simon Barber
2006-08-17 23:23           ` Ulrich Kunitz
2006-08-18  7:01           ` Johannes Berg [this message]
2006-08-18 16:45             ` Simon Barber
2006-08-21  6:45               ` Johannes Berg

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=1155884507.3425.5.camel@ux156 \
    --to=johannes@sipsolutions.net \
    --cc=dcbw@redhat.com \
    --cc=jt@hpl.hp.com \
    --cc=netdev@vger.kernel.org \
    --cc=simon@devicescape.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).