linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: Juan Carlos Garza Fernandez <juancarlosgarza@gmail.com>,
	linux-wireless@vger.kernel.org
Subject: Re: Status of the RTL8712 staging driver
Date: Tue, 02 Apr 2013 16:02:21 -0500	[thread overview]
Message-ID: <515B475D.2090709@lwfinger.net> (raw)
In-Reply-To: <201304021941.37133.chunkeey@googlemail.com>

On 04/02/2013 12:41 PM, Christian Lamparter wrote:
> On Tuesday, April 02, 2013 02:51:19 PM Juan Carlos Garza Fernandez wrote:
>> Now I have another question regarding the 8712 driver which has been
>> in staging forever.
>>
>> In your opinion, are there any chances that it will be improved to
>> reach the mainline level?

Yes, r8712u has been in staging for a long time; however, it is not a matter of 
improving it. For a new wireless driver to be included in the main wireless 
directories, it must use mac80211. Making the change from the current softmac in 
r8712u to a mac80211-based driver is essentially a complete rewrite. As r8712u 
functions quite well in station mode, I have not felt inclined to rework it for 
AP mode, particularly when a user can obtain a functioning router/AP for about 
$30. I feel that my time is better spent converting the drivers for Realtek 
devices that are not currently in the kernel. That list includes the rtl8723ae 
driver in 3.8, the rtl8188ee driver that will be in 3.10, and 3 other drivers 
that I currently have on my todo list.

Larry


  reply	other threads:[~2013-04-02 21:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-02 12:51 Status of the RTL8712 staging driver Juan Carlos Garza Fernandez
2013-04-02 17:41 ` Christian Lamparter
2013-04-02 21:02   ` Larry Finger [this message]
2013-04-03 12:31     ` Christian Lamparter
2013-04-03 14:38       ` Larry Finger

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=515B475D.2090709@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=chunkeey@googlemail.com \
    --cc=juancarlosgarza@gmail.com \
    --cc=linux-wireless@vger.kernel.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).