From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>,
linux-wireless <linux-wireless@vger.kernel.org>,
Christian Lamparter <chunkeey@googlemail.com>,
alexandre.f.demers@gmail.com, linville@tuxdriver.com
Subject: Re: r92su: status and will it be merged anytime soon?
Date: Mon, 04 Nov 2013 17:06:28 +0100 [thread overview]
Message-ID: <5277C604.1050604@gmail.com> (raw)
In-Reply-To: <5277BE84.7020808@lwfinger.net>
On 11/04/2013 04:34 PM, Larry Finger wrote:
>> _anything_ is better than a staging driver.
>>
>> There are distributions that don't build staging drivers.
>
> As a result, they force their users to build out-of-tree drivers!
reformulating: As a result, they force their users to _have a stable kernel_
Staging is only a working area. And the rtl8712-TODO is unreal:
- merge Realtek's bugfixes and new features into the driver
- switch to use LIB80211
- switch to use MAC80211
- checkpatch.pl fixes - only a few remain
>> So, please, replace and delete staging/rtl8712 with r92su.
>
> You seem not to understand. Any new wireless driver that does not
> use mac80211 *must* go into staging. AFAIK, that rule is absolute,
^^^^^^^^^^^^^^^^^^^^^
> and r92su cannot go into the regular wireless tree.
Who said that ? Then replace staging/rtl8712 with staging/r92su
Anyway, r92su is a _linux_ driver with a cfg80211 interface.
staging/rtl8712 is crap?
1152k drivers/staging/rtl8712/
340k r92su/
> If you do not like having drivers for RTL8192SU in staging, then
> write one that uses mac80211. You have access to as much information
> about the chips as anyone outside Realtek. They have no interest
> in doing the mac80211 version, and I have many other tasks with
> higher priority.
Nobody said that you have to write a rtl8712-mac80211.
But right now there is a better alternative, and it should be used.
next prev parent reply other threads:[~2013-11-04 16:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 14:17 r92su: status and will it be merged anytime soon? Xose Vazquez Perez
2013-11-04 14:21 ` Johannes Berg
2013-11-04 15:34 ` Larry Finger
2013-11-04 15:47 ` Christian Lamparter
2013-11-04 16:04 ` Johannes Berg
2013-11-04 16:15 ` Joshua Roys
2013-11-04 16:19 ` Christian Lamparter
2013-11-04 18:32 ` Johannes Berg
2013-11-04 19:10 ` Alexandre Demers
2013-11-04 16:06 ` Xose Vazquez Perez [this message]
2013-11-04 16:22 ` Larry Finger
-- strict thread matches above, loose matches on Subject: below --
2013-11-02 20:19 Alexandre Demers
2013-11-02 21:50 ` Christian Lamparter
2013-11-02 21:53 ` Larry Finger
2013-11-02 22:36 ` Alexandre Demers
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=5277C604.1050604@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=alexandre.f.demers@gmail.com \
--cc=chunkeey@googlemail.com \
--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