From: Larry Finger <Larry.Finger@lwfinger.net>
To: Walter Goldens <goldenstranger@yahoo.com>
Cc: "Gábor Stefanik" <netrolller.3d@gmail.com>,
"John W. Linville" <linville@tuxdriver.com>,
"Stefan Lippers-Hollmann" <s.L-H@gmx.de>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: Realtek rtl8188 support?
Date: Sun, 31 Oct 2010 10:04:14 -0500 [thread overview]
Message-ID: <4CCD856E.9010006@lwfinger.net> (raw)
In-Reply-To: <699923.49894.qm@web56805.mail.re3.yahoo.com>
On 10/31/2010 06:30 AM, Walter Goldens wrote:
>> Perhaps not, but I want to have one that works before
>> removing the staging driver.
>>
>> I think Realtek is serious. After the r8712u driver was
>> ready for inclusion in
>> staging, I sent them a copy of my revisions to their code.
>> Obviously, they
>> studied it. When I received the new code for a
>> mac80211-based driver for the
>> RTL8192CE driver, it was pretty clean and the sort of
>> changes that were needed
>> for the 8712 had already been done. After only a few hours
>> work, the sparse and
>> checkpatch warnings and errors were fixed. As far as I can
>> tell, this code is
>
> By "this code" you mean the code for the PCI chips or the USB ones? This topic here mostly touches on the USB cards, which is why I'm asking. And does that mean you'll include the driver once you've tested the cards?
I mean the PCIe devices. I plan to submit that driver in time to make the 2.6.38
merge. Realtek has not yet sent me the code for the USB devices, but as the chip
and core code is common, it should not be far behind.
Larry
next prev parent reply other threads:[~2010-10-31 15:03 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
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 [this message]
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=4CCD856E.9010006@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=goldenstranger@yahoo.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netrolller.3d@gmail.com \
--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 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.