From: "Gábor Stefanik" <netrolller.3d@gmail.com>
To: Walter Goldens <goldenstranger@yahoo.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Stefan Lippers-Hollmann <s.L-H@gmx.de>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: Realtek rtl8188 support?
Date: Fri, 29 Oct 2010 23:27:38 +0200 [thread overview]
Message-ID: <AANLkTimnuHM3E3G=d+R4-b=1NDkdEQ9jkbQsqB9ASiEC@mail.gmail.com> (raw)
In-Reply-To: <694082.86488.qm@web56803.mail.re3.yahoo.com>
On Fri, Oct 29, 2010 at 10:26 PM, Walter Goldens
<goldenstranger@yahoo.com> wrote:
>> With both devices the connection is stable and quite
>> performant (~9 MB/s,
>> short distance, little channel overlap) against an Atheros/
>> athk9 based
>> router running OpenWrt (HT20 && HT40-, b/g/n). In
>> comparison to rtl8192su
>> the authentification handshake succeeds a lot quicker and
>> without needing
>> retries, performance is comparable.
>
> Now, that we're in the habit of adding staging drivers to compat-wireless, shouldn't this one follow the likes of ath6kl and brcm80211? Surely lots of users will benefit from this.
AFAIK we only add staging drivers that will eventually move out of
staging. r8712 has no chance of ever leaving staging; a completely new
driver needs to be written (because it isn't mac80211-based).
>
> Walter
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
next prev parent reply other threads:[~2010-10-29 21:28 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-06 17:45 Realtek rtl8188 support? Paul Thomas
2010-03-06 18:07 ` Gábor Stefanik
2010-03-07 8:16 ` Pavel Roskin
2010-03-07 15:36 ` Gábor Stefanik
2010-03-10 1:59 ` Pavel Roskin
2010-03-10 3:16 ` Pavel Roskin
2010-03-29 22:19 ` Paul Thomas
2010-03-29 23:32 ` Gábor Stefanik
2010-05-25 0:16 ` Paul Thomas
2010-05-25 23:00 ` Frederic Leroy
2010-05-26 22:06 ` Pavel Roskin
2010-05-26 22:21 ` Gábor Stefanik
2010-05-28 16:35 ` Pavel Roskin
2010-09-10 11:29 ` Claus Ried
2010-09-18 3:37 ` Hin-Tak Leung
2010-09-18 13:43 ` Stefan Lippers-Hollmann
[not found] ` <AANLkTimz6bR7mLnEgeBzBZrbKC+jp2bx3VTya=YL2KjV@mail.gmail.com>
[not found] ` <201009212120.07914.s.L-H@gmx.de>
2010-10-28 18:26 ` Larry Finger
2010-10-28 21:48 ` Stefan Lippers-Hollmann
2010-10-28 22:10 ` Larry Finger
2010-10-29 20:02 ` Stefan Lippers-Hollmann
2010-10-29 20:03 ` staging: r8712u: Fix external firmware loading Stefan Lippers-Hollmann
2010-10-29 20:26 ` Realtek rtl8188 support? Walter Goldens
2010-10-29 21:27 ` Gábor Stefanik [this message]
2010-10-30 4:06 ` Larry Finger
2010-10-30 14:49 ` John W. Linville
2010-10-30 18:11 ` Gábor Stefanik
2010-10-31 3:44 ` Larry Finger
2010-10-31 11:30 ` Walter Goldens
2010-10-31 15:04 ` Larry Finger
2010-12-16 13:25 ` Walter Goldens
2010-12-16 14:10 ` Larry Finger
2011-01-25 7:57 ` Brian Prodoehl
2010-09-18 23:02 ` Paul Thomas
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='AANLkTimnuHM3E3G=d+R4-b=1NDkdEQ9jkbQsqB9ASiEC@mail.gmail.com' \
--to=netrolller.3d@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=goldenstranger@yahoo.com \
--cc=linux-wireless@vger.kernel.org \
--cc=s.L-H@gmx.de \
/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).