From: Solomon Peachy <pizza@shaftnet.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Greg KH <gregkh@linuxfoundation.org>,
linux-wireless@vger.kernel.org
Subject: Re: future of prism2_usb (aka wlan-ng) in staging tree
Date: Thu, 7 Nov 2013 13:57:14 -0500 [thread overview]
Message-ID: <20131107185714.GD12612@shaftnet.org> (raw)
In-Reply-To: <20131107175201.GA2002@tuxdriver.com>
[-- Attachment #1: Type: text/plain, Size: 1961 bytes --]
On Thu, Nov 07, 2013 at 12:52:02PM -0500, John W. Linville wrote:
> I haven't looked at the driver in question in a long time. Are there
> actually any users?
I honestly don't know who all uses it these days, since it's
802.11b-only and being USB, eminantly replacable with something more
modern.
Still, the driver and hardware works, and it's no more obsolete than the
likes of hostap, orinoco, aironet, zd1201, and others -- All of which
live on under net/wireless even though they still lack cfg80211 support.
BTW, this is my current WIP diffstat:
drivers/staging/wlan-ng/Makefile | 2
drivers/staging/wlan-ng/hfa384x.h | 2
drivers/staging/wlan-ng/hfa384x_usb.c | 67 ++----
drivers/staging/wlan-ng/p80211conv.c | 70 ------
drivers/staging/wlan-ng/p80211metadef.h | 3
drivers/staging/wlan-ng/p80211metastruct.h | 9
drivers/staging/wlan-ng/p80211netdev.c | 79 +++----
drivers/staging/wlan-ng/p80211netdev.h | 35 ---
drivers/staging/wlan-ng/prism2fw.c | 86 +++----
drivers/staging/wlan-ng/prism2mgmt.c | 126 ++++-------
drivers/staging/wlan-ng/prism2mib.c | 64 ++---
drivers/staging/wlan-ng/prism2sta.c | 118 ++++------
drivers/staging/wlan-ng/p80211ioctl.h | 89 -------
drivers/staging/wlan-ng/p80211req.c | 251 ----------------------
drivers/staging/wlan-ng/p80211req.h | 53 ----
drivers/staging/wlan-ng/p80211wep.c | 301 ---------------------------
16 files changed, 248 insertions(+), 1107 deletions(-)
Aside from fixing up a boatload of checkpatch warnings, I've been
stripping out more legacy cruft (eg custom ioctl, host-side WEP, more
plumbing) that's not relevant any longer.
- Solomon
--
Solomon Peachy pizza at shaftnet dot org
Delray Beach, FL ^^ (email/xmpp) ^^
Quidquid latine dictum sit, altum viditur.
[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2013-11-07 18:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 16:05 future of prism2_usb (aka wlan-ng) in staging tree Solomon Peachy
[not found] ` <527BC04F.2080000@lwfinger.net>
2013-11-07 16:37 ` Solomon Peachy
2013-11-07 17:52 ` John W. Linville
2013-11-07 18:57 ` Solomon Peachy [this message]
2013-11-07 19:11 ` John W. Linville
2013-11-07 19:46 ` Solomon Peachy
2013-11-07 22:25 ` Dan Williams
2013-11-07 23:02 ` Solomon Peachy
2013-11-07 23:37 ` Dan Williams
2013-11-08 13:46 ` Solomon Peachy
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=20131107185714.GD12612@shaftnet.org \
--to=pizza@shaftnet.org \
--cc=Larry.Finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).