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: Fri, 8 Nov 2013 08:46:32 -0500 [thread overview]
Message-ID: <20131108134632.GB13255@shaftnet.org> (raw)
In-Reply-To: <1383867422.2391.10.camel@dcbw.foobar.com>
[-- Attachment #1: Type: text/plain, Size: 806 bytes --]
On Thu, Nov 07, 2013 at 05:37:02PM -0600, Dan Williams wrote:
> > 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...
I'd started to write a more detailed history of the somewhat inbred
HFA384x chipsets, but eh, it's not particularly relevant. Suffice it to
say that the differences between the Orinoco and Prism2.5/3 USB hardware
are enough to make trying to support both with a single codebase an
insane proposition.
- 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 --]
prev parent reply other threads:[~2013-11-08 13:46 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
2013-11-08 13:46 ` Solomon Peachy [this message]
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=20131108134632.GB13255@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;
as well as URLs for NNTP newsgroup(s).