mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Holden Karau" <holden@pigscanfly.ca>
To: simon@thekelleys.org.uk
Cc: netdev <netdev@vger.kernel.org>,
	atmelwlandriver-devel@lists.sourceforge.net, holdenk@xandros.com,
	linux-kernel@vger.kernel.org
Subject: [PATCH] 2.6.18 atmel iwlist stats patch
Date: Thu, 28 Sep 2006 14:22:30 -0400	[thread overview]
Message-ID: <f46018bb0609281122l6998bed8raacd50a353c3c3fd@mail.gmail.com> (raw)

From: Holden Karau <holden@pigscanfly.ca> http://www.holdenkarau.com

I have made a small patch for the atmel driver [included in the 2.6.18
kernel] to output signal strength information as part of iwlist scan
[before it did not output any signal strength related information].
Signed-off-by: Holden Karau <holden@pigscanfly.ca> http://www.holdenkarau.com
--
The output of iwlist scan is frequently used by user space utilites to
chose which wireless network to connect to based on the reported
signal strength, so I think this could be useful [of course I could be
horribly wrong about that but *shrugs*]. Incase the patch gets mangled
I've also put it up on at
http://www.holdenkarau.com/~holden/projects/atmel/patches/001-iwlist-stats.patch
And now for the patch:
--- drivers/net/wireless/atmel.c.orig	2006-09-28 14:14:42.000000000 -0400
+++ drivers/net/wireless/atmel.c	2006-09-28 14:14:55.000000000 -0400
@@ -2345,6 +2345,14 @@ static int atmel_get_scan(struct net_dev
 		iwe.u.freq.e = 0;
 		current_ev = iwe_stream_add_event(current_ev, extra +
IW_SCAN_MAX_DATA, &iwe, IW_EV_FREQ_LEN);

+		/* Add quality statistics */
+		iwe.cmd = IWEVQUAL;
+		iwe.u.qual.level = (__u8) priv->BSSinfo[i].RSSI;
+		iwe.u.qual.qual  = iwe.u.qual.level;
+		/* iwe.u.qual.noise  = SOMETHING */
+		current_ev = iwe_stream_add_event(current_ev, extra +
IW_SCAN_MAX_DATA , &iwe, IW_EV_QUAL_LEN);
+
+
 		iwe.cmd = SIOCGIWENCODE;
 		if (priv->BSSinfo[i].UsingWEP)
 			iwe.u.data.flags = IW_ENCODE_ENABLED | IW_ENCODE_NOKEY;

                 reply	other threads:[~2006-09-28 18:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=f46018bb0609281122l6998bed8raacd50a353c3c3fd@mail.gmail.com \
    --to=holden@pigscanfly.ca \
    --cc=atmelwlandriver-devel@lists.sourceforge.net \
    --cc=holdenk@xandros.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=simon@thekelleys.org.uk \
    /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

all inboxes | Powered by JetHome®