From: bruno randolf <bruno@thinktube.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: ath5k-devel@lists.ath5k.org, jirislaby@gmail.com,
mickflemm@gmail.com, linux-wireless@vger.kernel.org,
linville@tuxdriver.com, johannes@sipsolutions.net,
flamingice@sourmilk.net, jbenc@suse.cz,
"Ivan Seskar" <Seskar@winlab.rutgers.edu>,
"Jean Tourrilhes" <jt@hpl.hp.com>,
"Haris Kremo" <harisk@winlab.rutgers.edu>
Subject: Re: [PATCH] mac80211: use hardware flags for signal/noise units
Date: Thu, 27 Mar 2008 11:07:54 +0900 [thread overview]
Message-ID: <200803271107.54208.bruno@thinktube.com> (raw)
In-Reply-To: <43e72e890803261559keb944a1g48d93645db2f2e73@mail.gmail.com>
On Thursday 27 March 2008 07:59:11 Luis R. Rodriguez wrote:
> > + * @IEEE80211_HW_SIGNAL_UNSPEC:
> > + * Hardware can provide signal values but we don't know its units.
> > To be + * able to standardize between different devices we would like
> > linear + * values from 0-100. If possible please provide dB or dBm
> > instead. + *
> > + * @IEEE80211_HW_SIGNAL_DB:
> > + * Hardware gives signal values in dB, decibel difference from an
> > + * arbitrary, fixed reference. If possible please provide dBm
> > instead. + *
>
> Signal should given in either be in dBm or an unspecified value. Since
> we have "unspecified" not sure why we would have the "db" value. Can
> you clarify what the difference between "unspecified" and "db" would
> be? I don't think it makes sense to refer to signal with a "db" value,
> unless we want "singal" here to be able to mean SNR.
the best thing to specify is dBm and all drivers should try to do that. it's
the only absolute value which makes sense and can be compared between
different drivers and devices.
however as we know some drivers simply cannot provide that. instead they have
some form of RSSI - RSSI in general meaning nothing more than "received
signal strength indication", which could be *anything*: voltage, any numbers,
in dB or linear or whatever. RSSI does *not* in general mean SNR! for example
you might remember the values of prism54, they were somewhere around 200. or
prism2 cards which had something around 100 (it's been a while since i've
touched them, so that might have changed). as jean noted the values don't
even have to be linear - so i think we should remove that from the
definition.
so in the "unspecified" case we really don't know much about the units, in the
worst case we can't even assume that 1/2 the value will mean 1/2 of the
received signal strength. it's very hard to work with this values, but it's
better than nothing.
other cards might not have noise, so no absolute (dBm) measurement, but a form
of RSSI which is measured in dB (that is a logarithmic difference). in this
case we might not know which reference point the measurement is taken to, but
we know how it behaves: -3 dB means half of the signal strength. if you add a
6dB gain antenna you can expect to see the signal reading to increase by 6dB.
it's not strictly SNR (because we don't know the noise) but quite close to
it.
i think it's important to know the difference between this 3 cases i order to
make some sense of the values in userspace gui, roaming agents, mesh link
metrics, etc...
bruno
next prev parent reply other threads:[~2008-03-27 2:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 12:30 [PATCH] mac80211: use hardware flags for signal/noise units Bruno Randolf
2008-03-26 22:59 ` Luis R. Rodriguez
2008-03-27 0:19 ` Jean Tourrilhes
2008-03-27 2:47 ` bruno randolf
2008-03-27 16:52 ` Jean Tourrilhes
2008-03-31 6:32 ` bruno randolf
2008-03-31 17:47 ` Jean Tourrilhes
2008-04-02 3:06 ` bruno randolf
2008-04-02 23:19 ` Luis R. Rodriguez
2008-04-02 23:56 ` Jean Tourrilhes
2008-04-03 1:55 ` bruno randolf
2008-03-27 2:07 ` bruno randolf [this message]
2008-04-02 19:27 ` Luis R. Rodriguez
2008-04-03 2:05 ` bruno randolf
2008-03-27 12:47 ` Johannes Berg
2008-03-28 10:52 ` bruno randolf
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=200803271107.54208.bruno@thinktube.com \
--to=bruno@thinktube.com \
--cc=Seskar@winlab.rutgers.edu \
--cc=ath5k-devel@lists.ath5k.org \
--cc=flamingice@sourmilk.net \
--cc=harisk@winlab.rutgers.edu \
--cc=jbenc@suse.cz \
--cc=jirislaby@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=jt@hpl.hp.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--cc=mickflemm@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).