public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Solomon Peachy <pizza@shaftnet.org>
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, 07 Nov 2013 17:37:02 -0600	[thread overview]
Message-ID: <1383867422.2391.10.camel@dcbw.foobar.com> (raw)
In-Reply-To: <20131107230215.GF12612@shaftnet.org>

On Thu, 2013-11-07 at 18:02 -0500, Solomon Peachy wrote:
> 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.

Sorry, I see now I meant orinico_usb, not hostap...

Dan

> 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



  reply	other threads:[~2013-11-07 23:37 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
2013-11-07 23:37                 ` Dan Williams [this message]
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=1383867422.2391.10.camel@dcbw.foobar.com \
    --to=dcbw@redhat.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=pizza@shaftnet.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