From: Solomon Peachy <pizza@shaftnet.org>
To: Dan Williams <dcbw@redhat.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
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 18:02:15 -0500 [thread overview]
Message-ID: <20131107230215.GF12612@shaftnet.org> (raw)
In-Reply-To: <1383863100.2391.5.camel@dcbw.foobar.com>
[-- Attachment #1: Type: text/plain, Size: 1609 bytes --]
On Thu, Nov 07, 2013 at 04:25:00PM -0600, Dan Williams wrote:
> > At this point it's a more modern driver than the ones already in the
> > kernel, and I'm willing to maintain it if there's a point to doing so.
>
> What's the delta in device support between prism2_usb and the hostap
> driver's USB subdriver? Is there any overlap?
Given that there never was a hostap_usb, there's no overlap at all. If
you have a prism2.5/3 USB widget, you'll need prism2_usb to make it more
than a lousy paperweight.
Way back in the day I'd advocated for doing a USB port of hostap rather
than mainlining prism2_usb, strictly on a ROI basis, but the boots on
the ground chose the latter. Given that prism2_usb has slowly been
improved since then and hostap has largely been ignored, IMO the right
thing here is to get it out of staging by taking care of any outstanding
problems.
On a strict feature basis, hostap has the advantage of supporting AP
operation and WPA -- For the latter, prism2_usb just needs the cfg80211
and crypto layer hooks since it needs to be handled in software anyway.
As for AP operation -- Intersil never officially supported AP mode on
the USB devices, and while it worked unofficially, it wasn't terribly
stable. The same stabilitiy problems plagued monitor operation; my
theory at the time was that their USB "glue" silicon simply couldn't
keep up with the load.
- 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 23:02 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
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 [this message]
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=20131107230215.GF12612@shaftnet.org \
--to=pizza@shaftnet.org \
--cc=Larry.Finger@lwfinger.net \
--cc=dcbw@redhat.com \
--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