From: Edgar Toernig <froese@gmx.de>
To: andreamrl@tiscali.it
Cc: "Michael Wu" <flamingice@sourmilk.net>, linux-wireless@vger.kernel.org
Subject: Re: [rtl8185] driver working but some probs
Date: Sun, 18 Nov 2007 20:20:56 +0100 [thread overview]
Message-ID: <20071118202056.1525a0f7.froese@gmx.de> (raw)
In-Reply-To: <c68f135e0711180810v1e059528hdd82c5a1f44c2016@mail.gmail.com>
Andrea Merello wrote:
>
> > > First thing I noticed: the reported "Link Signal Level"
> > > from iwconfig was way off. It showed values around
> > > -170 dBm when it was sitting directly beside the AP.
> > > It was easy to fix:
> > >
> > > - rx_status.ssi = (flags2 >> 8) & 0x7F;
> > > + rx_status.ssi = (flags2 >> 8) & 0xFF;
> > >
> > > According to the 8180 datasheet, this field is 8 bit.
> > >
> > Ugh. The diagram (in the 8185 datasheet) shows that the rssi field is 7 bits
> > long while the table after it says 8 bits, and the two figures disagree on a
> > few other fields too. I'll fix that up..
Maybe the 8185 changed it so that the LSB of the RSSI is now
the antenna flag? Just guessing though, I couldn't find an
8185 manual...
> True, the datasheet is not consistent.
> However the last reference code I have from Realtek is
>
> signal=((*(priv->rxringtail+1))& (0xff0000))>>16;
>[...]
> Similar to rtl8187 this look at AGC, not RSSI, field to extract signal
> strength information.
Hmm... there's no AGC field (16:23) in the 8180 doc.
It says 16:31 reserved.
> signal =(95-signal )*100/65;
> }
> priv->wstats.qual.level = signal;
What is the range of these fields anyway? Some seem
to be 0-255 (-256+x dBm?), some 0-65 (65 best?), some
0-100 (percent?).
Ciao, ET.
next prev parent reply other threads:[~2007-11-18 19:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 22:20 [rtl8185] driver working but some probs Edgar Toernig
2007-11-18 3:57 ` Michael Wu
2007-11-18 16:10 ` Andrea Merello
2007-11-18 19:20 ` Edgar Toernig [this message]
2007-11-18 19:00 ` Edgar Toernig
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=20071118202056.1525a0f7.froese@gmx.de \
--to=froese@gmx.de \
--cc=andreamrl@tiscali.it \
--cc=flamingice@sourmilk.net \
--cc=linux-wireless@vger.kernel.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).