From: Christian Lamparter <chunkeey@googlemail.com>
To: Juan Carlos Garza Fernandez <juancarlosgarza@gmail.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>, linux-wireless@vger.kernel.org
Subject: Re: Status of the RTL8712 staging driver
Date: Tue, 2 Apr 2013 19:41:36 +0200 [thread overview]
Message-ID: <201304021941.37133.chunkeey@googlemail.com> (raw)
In-Reply-To: <CAMEN=G4gwKC5oTbJyDfU4QcnO+EAff+nGsj+++AH0ip4eVV3MA@mail.gmail.com>
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?
Hopefully yes. You can download a git-repository with the latest driver
from: <https://github.com/chunkeey/rtl8192su>
The latest incarnation "r92su" is currently the best bet on getting a
proper driver into the mainline. Unlike its predecessor rtl8192su it
uses cfg80211 directly (yes, unfortunately. it is a stand-alone driver
with no dependencies on rtlwifi).
what works with r92su:
Station Mode & passive monitor
802.11b/g/n (yes, HT is working - in both directions)
WEP40/104,TKIP and CCMP (WPA and WPA2 works)
Defragmentation
QoS/WMM
ERP
What isn't:
AD-Hoc
Fragmentation (also broken in r8712u... It would work, if the fw
wouldn't override the sequence counter on out-going frames)
SDIO transport
> If so, would it be possible to use it as an access point with HostAPD,
> or is it limited by the firmware?
Apparently there is a AP firmware. But you have to ask Realtek for the
right firmware.
Regards,
Christian
next prev parent reply other threads:[~2013-04-02 17:41 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 [this message]
2013-04-02 21:02 ` Larry Finger
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=201304021941.37133.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=Larry.Finger@lwfinger.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.