The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: David Gibson <hermes@gibson.dropbear.id.au>
To: linux-kernel@vger.kernel.org
Subject: Alternative driver for Lucent 802.11 cards
Date: Wed, 28 Feb 2001 16:04:39 +1100	[thread overview]
Message-ID: <20010228160439.A2730@linuxcare.com> (raw)

I've written a driver for the Lucent and Cabletron 802.11 cards, to
replace the wvlan_cs driver. I'm looking for people to test this
driver with as many card/firmware variations as possible.

The new driver doesn't use the Lucent HCF-Light code, and as a
consequence the code should be easier to follow. The locking is also
slightly more sophisticated in that this driver shouldn't leave IRQs
disabled for long periods of time like wvlan_cs can.

The driver is basically complete, although it lacks a few features of
wvlan_cs (some less used iwconfig settings). Currently it supports the
Lucent and Cabletron cards, and it partially works (no WEP) on at
least one Prism based card (the Farallon Skyline). I hope to make it
support the Apple Airport cards as well, eventually.

wvlan_cs, the linux-wlan driver and the NetBSD if_wi driver were all
used quite heavily as references in writing this driver. This driver
is written (currently) strictly for use with 2.4 - it won't work with
2.2 or with the out-of-the-kernel pcmcia modules (mostly for trivial
reasons).

Currently it's not nicely packaged. The various files can be grabbed
from:
	 http://www.linuxcare.com.au/dgibson/dldwd/
How to build and install the driver is left as an exercise to the
reader.

-- 
David Gibson, Technical Support Engineer, Linuxcare, Inc.
+61 2 6262 8990
dgibson@linuxcare.com.au http://www.linuxcare.com/ 
Linuxcare. Putting open source to work.

                 reply	other threads:[~2001-02-28  5:05 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=20010228160439.A2730@linuxcare.com \
    --to=hermes@gibson.dropbear.id.au \
    --cc=linux-kernel@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