linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: nick@nhthomas.freeserve.co.uk
To: linux-wireless@vger.kernel.org
Subject: Wifi signal level differences
Date: Wed, 8 May 2013 15:51:44 +0200 (CEST)	[thread overview]
Message-ID: <7566504.38231368021104217.JavaMail.www@wwinf3714> (raw)

Hi,

I have an Atheros ath6kl_usb based wifi dongle.
I am using it with an embedded project.

The driver code can be built for either X86 or sh4 hardware - so I can also use the same USB wifi dongle on my Fedora 12 Linux PC or plugged in to the embedded device.
It's working fine in both situations.

But, I notice that the signal level reported in /proc/net/wireless is slightly different between the two units.
Note, I am using the same physical Atheros wifi dongle, and moving it from one device to the other to this test.

I notice that when using the X86 PC I see a signal level of -61, which is marginally better than the -66 I see in the embedded device.

I know that this isn't an exact science - but using a short USB extension lead I can orientate the wifi dongle to be in the same place and orientation when plugged in to either device.
So, I would expect the wifi signal strength to be reported the same !?

I know there are many differences between my Fedora 12 PC, and the embedded STLinux project - not least that the driver is compiled using different compilers.

But, I was wondering what else could explain the difference in signal levels between the two?

Also, which part of the driver code is responsible for reading/calculating the signal level value?


Regards

Nick

             reply	other threads:[~2013-05-08 13:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-08 13:51 nick [this message]
2013-05-08 14:29 ` Wifi signal level differences Dan Williams
2013-05-08 14:42   ` nick
2013-05-15 13:19   ` Kalle Valo

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=7566504.38231368021104217.JavaMail.www@wwinf3714 \
    --to=nick@nhthomas.freeserve.co.uk \
    --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).