From: Brian Prodoehl <bprodoehl@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: "Walter Goldens" <goldenstranger@yahoo.com>,
"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: Tue, 25 Jan 2011 02:57:39 -0500 [thread overview]
Message-ID: <AANLkTim5_NGoUK4tWyyaXEWzWSGoE4wYu+fzMf-y7ivA@mail.gmail.com> (raw)
In-Reply-To: <4D0A1DD6.8050500@lwfinger.net>
On Thu, Dec 16, 2010 at 9:10 AM, Larry Finger <Larry.Finger@lwfinger.net> wrote:
> On 12/16/2010 07:25 AM, Walter Goldens wrote:
>> 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.
>
>> Hey Larry,
>>
>> Whats the status quo for the USB driver?
>
> Realtek is still testing/finishing. They sent me the firmware, which I pushed to
> linux-firmware, thus that part is ready.
>
> As we just got the code for the PCIe version into wireless-testing yesterday, I
> hope that the good news on it will help the USB effort.
>
> Larry
Any word on a mac80211-based driver for the RTL8191SE? PCIe,
vendor/device is 10ec:8172 (comes standard in a lot of new Toshiba
laptops). The RTL8191SE and RTL8192SE use the same driver and
firmware from Realtek. That driver from Realtek is sort of similar to
Realtek's RTL8192CE driver, but, functionally, they look different
enough that I really doubt it would just work if I added the
vendor/device pair and got the rtl8192ce driver to load the right
firmware for the RTL8192SE.
-Brian
next prev parent reply other threads:[~2011-01-25 7:57 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
2010-12-16 13:25 ` Walter Goldens
2010-12-16 14:10 ` Larry Finger
2011-01-25 7:57 ` Brian Prodoehl [this message]
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=AANLkTim5_NGoUK4tWyyaXEWzWSGoE4wYu+fzMf-y7ivA@mail.gmail.com \
--to=bprodoehl@gmail.com \
--cc=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 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).