From: bruno randolf <bruno@thinktube.com>
To: jt@hpl.hp.com
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
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>,
Haris Kremo <harisk@winlab.rutgers.edu>
Subject: Re: [PATCH] mac80211: use hardware flags for signal/noise units
Date: Wed, 2 Apr 2008 12:06:24 +0900 [thread overview]
Message-ID: <200804021206.24626.bruno@thinktube.com> (raw)
In-Reply-To: <20080331174756.GA9882@bougret.hpl.hp.com>
On Tuesday 01 April 2008 02:47:56 Jean Tourrilhes wrote:
> > do you think it would be feasible
> > to require the drivers to normalize their RSSI to a range of 0-100,
> > so we would have at least some consistency between devices? (of
> > course their steps within this percentage would be different and it
> > would still be impossible to compare these values across different
> > devices).
>
> If the measurement is not linear or log, it does not make
> sense mandating the 0-100, because 50 won't be the mid-point. And we
> assume that devices are not consistent to start with...
> Anyway, to avoid quantisation errors, I prefer to defer
> normalisation to the end software. For example, if the app use a 64
> pixel window to show the RSSI, it wants a value 0-63, not 0-100.
ok, got it :) i will keep max_signal for this, then. it should be used for
IEEE80211_HW_SIGNAL_UNSPEC and IEEE80211_HW_SIGNAL_DB. in the case of dBm i
think we can always assume the same range.
cheers,
bruno
next prev parent reply other threads:[~2008-04-02 3:06 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 [this message]
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
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=200804021206.24626.bruno@thinktube.com \
--to=bruno@thinktube.com \
--cc=Seskar@winlab.rutgers.edu \
--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).