From: Ivo van Doorn <ivdoorn@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
radiotap@mail.ojctech.com,
"Ivan Seskar" <Seskar@winlab.rutgers.edu>,
"Haris Kremo" <harisk@winlab.rutgers.edu>,
"John W. Linville" <linville@tuxdriver.com>,
"Simon Barber" <simon@devicescape.com>,
"Dan Williams" <dcbw@redhat.com>,
"Luis Carlos Cobo" <luisca@cozybit.com>,
"Javier Cardona" <javier@cozybit.com>,
"Sam Leffler" <sam@errno.com>, "Jean Tourrilhes" <jt@hpl.hp.com>,
"Stefano Brivio" <stefano.brivio@polimi.it>,
"Johannes Berg" <johannes@sipsolutions.net>
Subject: Re: [RFC] RCPI support in radiotap and in our wireless subsystems
Date: Thu, 6 Mar 2008 21:55:17 +0100 [thread overview]
Message-ID: <200803062155.19725.IvDoorn@gmail.com> (raw)
In-Reply-To: <43e72e890803061238u50847f1fs587627c5fac028d6@mail.gmail.com>
Hi.
> ---
>
> For ipw2200:
>
> s8 antsignal = frame->rssi_dbm - IPW_RSSI_TO_DBM;
>
> and IPW_RSSI_TO_DBM is set to 112.
>
> Is antsignal above the "measure by the PHY sublayer of the received RF
> power in the channel measured over the entire received frame"?
For completeness, the rt2x00 & RSSI:
rt2400pci, rt2500pci, rt2500usb:
Same as ipw2200 only the IPW_RSSI_TO_DBM varies from 100 to 120 (as
hardcoded value in the register) to a unsigned char value read from
the EEPROM. The legacy drivers _suggest_ this is the rssi...
rt61pci, rt73usb:
The device reports an agc value, this is used as basis for a vague calculation
to determine the RSSI_TO_DBM offset based on LNA and current operating band.
Here too, the legacy driver suggests this is the rssi...
Ivo
next prev parent reply other threads:[~2008-03-06 20:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 20:38 [RFC] RCPI support in radiotap and in our wireless subsystems Luis R. Rodriguez
2008-03-06 20:55 ` Ivo van Doorn [this message]
2008-03-07 0:32 ` bruno randolf
2008-03-07 3:04 ` Luis R. Rodriguez
2008-03-07 8:57 ` bruno randolf
2008-03-07 15:41 ` Luis R. Rodriguez
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=200803062155.19725.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=Seskar@winlab.rutgers.edu \
--cc=dcbw@redhat.com \
--cc=harisk@winlab.rutgers.edu \
--cc=javier@cozybit.com \
--cc=johannes@sipsolutions.net \
--cc=jt@hpl.hp.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=luisca@cozybit.com \
--cc=mcgrof@gmail.com \
--cc=radiotap@mail.ojctech.com \
--cc=sam@errno.com \
--cc=simon@devicescape.com \
--cc=stefano.brivio@polimi.it \
/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).