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 16:25:00 -0600 [thread overview]
Message-ID: <1383863100.2391.5.camel@dcbw.foobar.com> (raw)
In-Reply-To: <20131107194641.GE12612@shaftnet.org>
On Thu, 2013-11-07 at 14:46 -0500, Solomon Peachy wrote:
> On Thu, Nov 07, 2013 at 02:11:23PM -0500, John W. Linville wrote:
> > And all of which were nominated by someone (possibly me) to be shuffled
> > out of the tree due to lack of users and unknown functional status...
>
> Heh, fair enough!
>
> > I don't want to discourage anyone from working on something that
> > scratches their itch, especially if you have working hardware and
> > some users. OTOH, I'd rather not add a long term support burden to
> > the kernel if nobody is going to use it...?
>
> On an average month the linux-wlan-ng repository I still host gets 3-4K
> non-spider hits for the USB firmware files, so in this particular case
> there are still users out there.
>
> 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?
Dan
next prev parent reply other threads:[~2013-11-07 22:25 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 [this message]
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=1383863100.2391.5.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;
as well as URLs for NNTP newsgroup(s).