linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Kilroy <kilroyd@googlemail.com>
To: linux-wireless@vger.kernel.org
Cc: orinoco-devel@lists.sourceforge.net,
	David Kilroy <kilroyd@googlemail.com>
Subject: [RFC 0/5] orinoco: Add support for Agere based USB cards
Date: Mon, 19 Apr 2010 08:35:17 +0100	[thread overview]
Message-ID: <1271662522-29119-1-git-send-email-kilroyd@googlemail.com> (raw)

This patch series adds the orinoco_usb driver, originally written by
Manuel Estrada Sainz.

I believe the main stumbling block the last time this driver was
submitted for inclusion was the way it handled the orinoco driver
locking. I've reworked this into something reasonably sane (patch 3).

The resulting driver has been basically tested with a Compaq WL215
(thanks to Mark Davis for supplying one). Managed mode with WEP works
on this card while a WPA-enabled PCMCIA orinoco card is running.

I'm not familiar with the USB subsystem, so there may be issues that
need to be resolved in that area. Also the original driver used
in_atomic in one location. I left this as-is in the main driver
commit (patch 4), and the subsequent patch (5) is my attempt to fix
this up. It works, but there may be a better way to do this.


Regards,

Dave.

---
David Kilroy (5):
  orinoco: add hermes_ops
  orinoco: allow driver to specify netdev_ops
  orinoco: encapsulate driver locking
  orinoco: add orinoco_usb driver
  orinoco_usb: avoid in_atomic

 drivers/net/wireless/orinoco/Kconfig          |    7 +
 drivers/net/wireless/orinoco/Makefile         |    1 +
 drivers/net/wireless/orinoco/airport.c        |    4 +-
 drivers/net/wireless/orinoco/cfg.c            |    2 +-
 drivers/net/wireless/orinoco/fw.c             |    2 +-
 drivers/net/wireless/orinoco/hermes.c         |   76 +-
 drivers/net/wireless/orinoco/hermes.h         |   55 +-
 drivers/net/wireless/orinoco/hermes_dld.c     |   34 +-
 drivers/net/wireless/orinoco/hw.c             |   63 +-
 drivers/net/wireless/orinoco/main.c           |  129 ++-
 drivers/net/wireless/orinoco/orinoco.h        |   30 +-
 drivers/net/wireless/orinoco/orinoco_cs.c     |    2 +-
 drivers/net/wireless/orinoco/orinoco_nortel.c |    2 +-
 drivers/net/wireless/orinoco/orinoco_pci.c    |    2 +-
 drivers/net/wireless/orinoco/orinoco_plx.c    |    2 +-
 drivers/net/wireless/orinoco/orinoco_tmd.c    |    2 +-
 drivers/net/wireless/orinoco/orinoco_usb.c    | 1678 +++++++++++++++++++++++++
 drivers/net/wireless/orinoco/spectrum_cs.c    |    2 +-
 drivers/net/wireless/orinoco/wext.c           |    6 +-
 19 files changed, 1932 insertions(+), 167 deletions(-)
 create mode 100644 drivers/net/wireless/orinoco/orinoco_usb.c


             reply	other threads:[~2010-04-19  7:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-19  7:35 David Kilroy [this message]
2010-04-19  7:35 ` [RFC 1/5] orinoco: add hermes_ops David Kilroy
2010-04-19  7:35 ` [RFC 2/5] orinoco: allow driver to specify netdev_ops David Kilroy
2010-04-19  7:35 ` [RFC 3/5] orinoco: encapsulate driver locking David Kilroy
2010-04-19  7:35 ` [RFC 4/5] orinoco: add orinoco_usb driver David Kilroy
2010-04-19  7:35 ` [RFC 5/5] orinoco_usb: avoid in_atomic David Kilroy

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=1271662522-29119-1-git-send-email-kilroyd@googlemail.com \
    --to=kilroyd@googlemail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=orinoco-devel@lists.sourceforge.net \
    /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).