From: "Luis R. Rodriguez" <mcgrof-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: bruno randolf <bruno-L9ZBdB2wSWtl57MIdRCFDg@public.gmane.org>
Cc: linux-wireless
<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
radiotap-rN9S6JXhQ+WXmMXjJBpWqg@public.gmane.org,
Ivan Seskar
<Seskar-NvJAj8134tRxEa0u/P/EHDe48wsgrGvP@public.gmane.org>,
Haris Kremo
<harisk-NvJAj8134tRxEa0u/P/EHDe48wsgrGvP@public.gmane.org>,
"John W. Linville"
<linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>,
Simon Barber <simon-r/za7OOdgF0ztatW0fm/fQ@public.gmane.org>,
Dan Williams <dcbw-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Luis Carlos Cobo <luisca-W/OLz77bvjtBDgjK7y7TUQ@public.gmane.org>,
Javier Cardona <javier-W/OLz77bvjtBDgjK7y7TUQ@public.gmane.org>,
Sam Leffler <sam-zZXckVAlHaQAvxtiuMwx3w@public.gmane.org>,
Jean Tourrilhes <jt-sDzT885Ts8HQT0dZR+AlfA@public.gmane.org>,
Stefano Brivio
<stefano.brivio-hl5o88x/ua9eoWH0uzbU5w@public.gmane.org>,
Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
Subject: Re: [RFC] RCPI support in radiotap and in our wireless subsystems
Date: Fri, 7 Mar 2008 10:41:26 -0500 [thread overview]
Message-ID: <43e72e890803070741q1e2558c2odb0046f7e519fc07__19695.3906016008$1216696541$gmane$org@mail.gmail.com> (raw)
In-Reply-To: <200803071757.19302.bruno-L9ZBdB2wSWtl57MIdRCFDg@public.gmane.org>
On Fri, Mar 7, 2008 at 3:57 AM, bruno randolf <bruno-L9ZBdB2wSWtl57MIdRCFDg@public.gmane.org> wrote:
> On Friday 07 March 2008 12:04:24 Luis R. Rodriguez wrote:
> > > it could be changed to something like:
> > >
> > > * @signal: signal strength in dBm above noise or RCPI according to flag
> >
> > As it stands I don't think all drivers could populate this field under
> > that description. For example, ssi in b43 is set to some magical value
> > we have no clue what it means.
> >
> > We *could* test this stuff and see if it matches RCPI for each device,
> > or just try to figure out at least what RSSI is wrt to the observed
> > signal through a spectrum analyser (and even jssi is for b43) but I
> > wonder how this will change upon hw revisions.
> >
> > > * @noise: PHY noise in dBm when receiving this frame
> > > (remove ssi)
> >
> > Again, the problem in clarifying this also puts a restriction on what
> > driver developers may know about their hardware.
>
> yes, but you suggested RCPI which is even more difficult to deliver. well - i
> don't know *any* device which could...
Well I was hoping we could see if we *could* deliver it, at least
within Atheros hardware but from what you tell me we can't. And from
what I gather from a few other wireless cards we can't either. The
idea was to propose it for radiotap but I do think its pointless if we
don't have hardware yet which we can produce those results.
> ok. what about 3 hw flags then?
>
> something like:
> _SIGNAL_RSSI_UNITLESS
> _SIGNAL_RSSI_DBM
> _SIGNAL_RCPI
Seems reasonable.
> so mac80211 can fill in the right radiotap headers, and drivers can make it
> clear what they support. it's clear that drivers should strive to deliver the
> most exact when they can.
Sounds good!
So having IEEE80211_RADIOTAP_DBM_ANTSIGNAL is preferable than
IEEE80211_RADIOTAP_DB_ANTSIGNAL in drivers, for obvious reasons. I'll
deal with another question with respect to mac80211 in another e-mail.
> we have the same problem with the rx timestamp. we made a definition and ath5k
> for example can't deliver. but i think a clear definition and a clear note
> where it cannot be delivered is better than no definition at all :)
Sure, we have to take into consideration what other drivers can deliver as well.
Luis
next prev parent reply other threads:[~2008-03-07 15:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43e72e890803061238u50847f1fs587627c5fac028d6@mail.gmail.com>
[not found] ` <43e72e890803061238u50847f1fs587627c5fac028d6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-03-06 20:55 ` [RFC] RCPI support in radiotap and in our wireless subsystems Ivo van Doorn
2008-03-07 0:32 ` bruno randolf
[not found] ` <200803070932.51396.bruno@thinktube.com>
[not found] ` <200803070932.51396.bruno-L9ZBdB2wSWtl57MIdRCFDg@public.gmane.org>
2008-03-07 3:04 ` Luis R. Rodriguez
[not found] ` <43e72e890803061904h742df37fuaa12977c45e457a@mail.gmail.com>
[not found] ` <43e72e890803061904h742df37fuaa12977c45e457a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-03-07 8:57 ` bruno randolf
[not found] ` <200803071757.19302.bruno@thinktube.com>
[not found] ` <200803071757.19302.bruno-L9ZBdB2wSWtl57MIdRCFDg@public.gmane.org>
2008-03-07 15:41 ` Luis R. Rodriguez [this message]
2008-03-06 20:38 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='43e72e890803070741q1e2558c2odb0046f7e519fc07__19695.3906016008$1216696541$gmane$org@mail.gmail.com' \
--to=mcgrof-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=Seskar-NvJAj8134tRxEa0u/P/EHDe48wsgrGvP@public.gmane.org \
--cc=bruno-L9ZBdB2wSWtl57MIdRCFDg@public.gmane.org \
--cc=dcbw-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=harisk-NvJAj8134tRxEa0u/P/EHDe48wsgrGvP@public.gmane.org \
--cc=javier-W/OLz77bvjtBDgjK7y7TUQ@public.gmane.org \
--cc=johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org \
--cc=jt-sDzT885Ts8HQT0dZR+AlfA@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
--cc=luisca-W/OLz77bvjtBDgjK7y7TUQ@public.gmane.org \
--cc=radiotap-rN9S6JXhQ+WXmMXjJBpWqg@public.gmane.org \
--cc=sam-zZXckVAlHaQAvxtiuMwx3w@public.gmane.org \
--cc=simon-r/za7OOdgF0ztatW0fm/fQ@public.gmane.org \
--cc=stefano.brivio-hl5o88x/ua9eoWH0uzbU5w@public.gmane.org \
/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).