public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Solomon Peachy <pizza@shaftnet.org>
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 12:52:02 -0500	[thread overview]
Message-ID: <20131107175201.GA2002@tuxdriver.com> (raw)
In-Reply-To: <20131107163719.GC12612@shaftnet.org>

On Thu, Nov 07, 2013 at 11:37:19AM -0500, Solomon Peachy wrote:
> On Thu, Nov 07, 2013 at 10:31:11AM -0600, Larry Finger wrote:
> > This seems like a good point to clarify what it takes for a wireless
> > driver to be added to net/wireless.
> > 
> > Is it necessary that any new softmac driver in net/wireless must use
> > mac80211, or is it sufficient that it implement cfg80211?
> 
> IMO a softmac driver should use mac80211 before being merged; there's no 
> sense in having multiple 802.11 stacks especially with the ever-growing 
> complexity of 802.11.
> 
> But in this particular case, prism2_usb/wlan-ng is perhaps the original 
> fullmac 802.11 device.  :)

We have long said that any softmac driver needs to be based on
mac80211.  We have also been saying for some time that any newly
merged drivers need to fully support cfg80211.  FWIW, I think that
we would actively discourage anyone from implementing any support at
all for wireless extensions -- shouldn't need that anyway with full
cfg80211 support..

I haven't looked at the driver in question in a long time.  Are there
actually any users?

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2013-11-07 18:00 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 [this message]
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

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=20131107175201.GA2002@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-wireless@vger.kernel.org \
    --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