From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: ksenija.stanojevic@gmail.com,
"driverdev-devel@linuxdriverproject.org"
<driverdev-devel@linuxdriverproject.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
Solomon Peachy <pizza@shaftnet.org>
Subject: Re: Move wlan-ng out of staging?
Date: Fri, 29 Jan 2016 17:11:04 +0100 [thread overview]
Message-ID: <56AB8F18.9000909@gmail.com> (raw)
In-Reply-To: <56AB8C90.2050909@gmail.com>
On 01/29/2016 05:00 PM, Xose Vazquez Perez wrote:
> Ksenija wrote:
>
>> I'm helping Greg do a bit of cleanup in the staging tree, I noticed that
>> wlan-ng driver is maybe ready to be moved out of staging. Are there
>> any TODO tasks left to do beside checkpatch.pl clean-up?
>
> Its FAQ was very clear: ftp://ftp.linux-wlan.org/pub/linux-wlan-ng/FAQ
> [archived at http://puppylinux.dreamhosters.com/wireless/linux-wlan-org_FAQ.txt ]
>
> --cut--
> Q: When will linux-wlan-ng be merged into the mainline kernel?
>
> Short answer: Never.
>
> First, the linux-netdev people will soundly reject this driver.
> I don't begrudge them for this; indeed in their position I'd do
> exactly the same. It's a sound engineering decision.
>
> linux-wlan-ng is obselete, and effort spent fixing it is better
> spent elsewhere. You can't even buy the hardware any longer.
>
> The original design for linux-wlan-ng was to separate the 802.11
> stack from the actual hardware driver. This added a lot of
> complexity, but would greatly ease the pain of supporitng
> multiple hardware types. Unfortunately, the implementation was
> turned out to be somewhat flawed, and hardware manufaturers went
> away from the thick-mac model, leaving linux-wlan-ng overly
> complex for what it did.
>
> (Ironically, the linux kernel is adopting a similar
> separation model, but it is a long way off from being ready)
>
> So why not rewrite linux-wlan-ng to be more suitable, the
> enterprising reader may ask?
>
> The kernel already has two drivers for prism2 (cs/pci/plx)
> hardware -- hostap and orinoco. linux-wlan-ng basically
> has three features not present in kernel drivers:
>
> 1) USB support
> 2) nearly complete implemettion of the 802.11 MIB/MLME
> 3) Firmware-based AP support
>
> (3) requires an expensive license that isn't even available any
> longer, as the hostap mode works far better -- and is already
> supported by in-kernel drivers.
>
> (2) would need to be removed or completely rewritten in order to
> be merged, as it does not fit within existing kernel APIs, and
> it would be effectively merging new kernel APIs.
>
> (1) Is the only truly unique thing that linux-wlan-ng does that
> is generally needed any more.
>
> To merge it into the kernel, we'd need to strip out (2), which
> would necessitate a complete rewrite -- to the point where
> writing a new driver from scratch is easier.
>
> Basically, it would take far less effort to add USB
> support to the in-kernel drivers than it would to make
> linux-wlan-ng acceptable to be merged.
>
> In other words, the short answer is: Never.
> --end--
>
Detailed info in these threads:
https://marc.info/?l=linux-wlan-user&m=125122113309475
https://marc.info/?l=linux-wireless&m=138384105903345
next prev parent reply other threads:[~2016-01-29 16:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 16:00 Move wlan-ng out of staging? Xose Vazquez Perez
2016-01-29 16:11 ` Xose Vazquez Perez [this message]
2016-01-29 19:24 ` Solomon Peachy
2016-01-29 16:13 ` Sudip Mukherjee
[not found] <CAL7P5j+iYzpnR+xT013A7AV=bQ8bSn4W1K=qjieFCAiv1YmwRw@mail.gmail.com>
[not found] ` <20160125181220.GJ5325@mwanda>
2016-01-27 18:27 ` Kalle Valo
2016-01-27 22:48 ` Julian Calaby
2016-01-27 23:07 ` Greg KH
2016-01-27 23:28 ` Julian Calaby
2016-01-27 23:32 ` Greg KH
2016-01-29 0:56 ` Julian Calaby
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=56AB8F18.9000909@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=ksenija.stanojevic@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).