linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kilroyd@googlemail.com
To: linux-wireless@vger.kernel.org
Cc: proski@gnu.org, orinoco-devel@lists.sourceforge.net,
	David Kilroy <kilroyd@gmail.com>
Subject: [RFC PATCH 01/19] orinoco: Add ESSID specific scanning for Agere fw
Date: Sat, 28 Jun 2008 19:38:07 +0100	[thread overview]
Message-ID: <1214678305-7057-2-git-send-email-kilroyd@gmail.com> (raw)
In-Reply-To: <1214678305-7057-1-git-send-email-kilroyd@gmail.com>

Pass the ESSID to the card.

This allows 'iwlist eth1 scan essid <essid>' to work, and will help
with routers setup not to broadcast the ESSID.

Signed-off-by: David Kilroy <kilroyd@gmail.com>
---
 drivers/net/wireless/orinoco.c |   20 +++++++++++++++++++-
 1 files changed, 19 insertions(+), 1 deletions(-)

diff --git a/drivers/net/wireless/orinoco.c b/drivers/net/wireless/orinoco.c
index b047306..e9dca96 100644
--- a/drivers/net/wireless/orinoco.c
+++ b/drivers/net/wireless/orinoco.c
@@ -2989,6 +2989,11 @@ static int orinoco_ioctl_getiwrange(struct net_device *dev,
 	range->min_r_time = 0;
 	range->max_r_time = 65535 * 1000;	/* ??? */
 
+	if (priv->firmware_type == FIRMWARE_TYPE_AGERE)
+		range->scan_capa = IW_SCAN_CAPA_ESSID;
+	else
+		range->scan_capa = IW_SCAN_CAPA_NONE;
+
 	/* Event capability (kernel) */
 	IW_EVENT_CAPA_SET_KERNEL(range->event_capa);
 	/* Event capability (driver) */
@@ -3958,6 +3963,7 @@ static int orinoco_ioctl_setscan(struct net_device *dev,
 {
 	struct orinoco_private *priv = netdev_priv(dev);
 	hermes_t *hw = &priv->hw;
+	struct iw_scan_req *si = (struct iw_scan_req *) extra;
 	int err = 0;
 	unsigned long flags;
 
@@ -4019,7 +4025,19 @@ static int orinoco_ioctl_setscan(struct net_device *dev,
 		}
 		break;
 		case FIRMWARE_TYPE_AGERE:
-			err = hermes_write_wordrec(hw, USER_BAP,
+			if (priv->scan_mode & IW_SCAN_THIS_ESSID) {
+				struct hermes_idstring idbuf;
+				size_t len = min(sizeof(idbuf.val),
+						 (size_t) si->essid_len);
+				idbuf.len = cpu_to_le16(len);
+				memcpy(idbuf.val, si->essid, len);
+
+				err = hermes_write_ltv(hw, USER_BAP,
+					       HERMES_RID_CNFSCANSSID_AGERE,
+					       HERMES_BYTES_TO_RECLEN(len + 2),
+					       &idbuf);
+			} else
+				err = hermes_write_wordrec(hw, USER_BAP,
 						   HERMES_RID_CNFSCANSSID_AGERE,
 						   0);	/* Any ESSID */
 			if (err)
-- 
1.5.4.5


  reply	other threads:[~2008-06-28 18:38 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-28 18:38 [RFC PATCH 00/19] orinoco: WPA for Agere based cards kilroyd
2008-06-28 18:38 ` kilroyd [this message]
2008-06-28 18:38   ` [RFC PATCH 02/19] orinoco: Update scan translation kilroyd
2008-06-28 18:38     ` [RFC PATCH 03/19] orinoco: Specify all three parameters to every Hermes command kilroyd
2008-06-28 18:38       ` [RFC PATCH 04/19] orinoco: Move EXPORT_SYMBOL declarations next to exported function kilroyd
2008-06-28 18:38         ` [RFC PATCH 05/19] orinoco: Add function to execute Hermes initialisation commands synchronously kilroyd
2008-06-28 18:38           ` [RFC PATCH 06/19] orinoco: Move firmware download functionality into new module kilroyd
2008-06-28 18:38             ` [RFC PATCH 07/19] orinoco: Make firmware download logic more generic kilroyd
2008-06-28 18:38               ` [RFC PATCH 08/19] orinoco: Extend hermes_dld routines for Agere firmware kilroyd
2008-06-28 18:38                 ` [RFC PATCH 09/19] orinoco: Invoke firmware download in main driver kilroyd
2008-06-28 18:38                   ` [RFC PATCH 10/19] orinoco: Fix transmit for Agere/Lucent with fw 9.x kilroyd
2008-06-28 18:38                     ` [RFC PATCH 11/19] orinoco: address checkpatch typedef warning kilroyd
2008-06-28 18:38                       ` [RFC PATCH 12/19] orinoco: Use extended Agere scans available on 9.x series firmwares kilroyd
2008-06-28 18:38                         ` [RFC PATCH 13/19] orinoco: Don't use boolean parameter to record encoding type kilroyd
2008-06-28 18:38                           ` [RFC PATCH 14/19] orinoco: Split wevent work thread from wevent sending kilroyd
2008-06-28 18:38                             ` [RFC PATCH 15/19] orinoco: Use a macro to define wireless handlers kilroyd
2008-06-28 18:38                               ` [RFC PATCH 16/19] orinoco: Add WE-18 ioctls for WPA kilroyd
2008-06-28 18:38                                 ` [RFC PATCH 17/19] orinoco: Send association events to userspace kilroyd
2008-06-28 18:38                                   ` [RFC PATCH 18/19] orinoco: Process bulk of receive interrupt in a tasklet kilroyd
2008-06-28 18:38                                     ` [RFC PATCH 19/19] orinoco: Add MIC on TX and check on RX kilroyd
2008-06-29 21:56                                       ` Harvey Harrison
2008-06-30 11:06                                         ` Johannes Berg
2008-06-30 18:09                                           ` Dave
2008-06-30 19:28 ` [RFC PATCH 00/19] orinoco: WPA for Agere based cards John W. Linville
2008-06-30 20:16   ` Dave
2008-08-01 23:49 ` [Orinoco-devel] " Pavel Roskin

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=1214678305-7057-2-git-send-email-kilroyd@gmail.com \
    --to=kilroyd@googlemail.com \
    --cc=kilroyd@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=orinoco-devel@lists.sourceforge.net \
    --cc=proski@gnu.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).