From: Igor Plyatov <plyatov@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
George <george0505@realtek.com>,
Johannes Berg <johannes.berg@intel.com>,
Chaoming Li <chaoming_li@realsil.com.cn>,
linux-wireless@vger.kernel.org
Subject: Re: net/wireless/rtlwifi: problem with D-link DWA-131 USB adapter
Date: Fri, 08 Apr 2011 19:06:10 +0400 [thread overview]
Message-ID: <4D9F2462.60600@gmail.com> (raw)
In-Reply-To: <4D9F14FE.8060905@lwfinger.net>
Dear Larry,
> The driver rtl8192cu is for the RTL8192CU/RTL8188CU chips. The DWA-131
> contains an RTL8192SU chip. It cannot be driven by rtl8192cu - it will
> never work.
>
> On my TODO list is the preparation of a driver named rtl8192su, but
> since r8712u works, the priority is low. I'm much more interested in
> getting the drivers for the RTL8192SE and RTL8192DE chips into the
> kernel. Note that rtl8192su will share a lot of code with rtl8192se in
> the same fashion that rtl8192ce and rtl8192cu share routines.
>
> When I prepared the r8712u driver for staging, I did not worry about
> the LED, which is why it doesn't blink. What kind of LED action do you
> prefer. Some users only want the LED on when the interface is active
> and complain when it blinks. Others want it to blink when transmitting.
>
> Larry
Thank you for descriptive answer!
Is there any way to detect Realtek chipset type by some means like lsusb
or else?
Best regards!
--
Igor Plyatov
next prev parent reply other threads:[~2011-04-08 15:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 13:29 net/wireless/rtlwifi: problem with D-link DWA-131 USB adapter Igor Plyatov
2011-04-08 14:00 ` Larry Finger
2011-04-08 15:06 ` Igor Plyatov [this message]
2011-04-08 15:46 ` Larry Finger
2011-04-08 16:11 ` Igor Plyatov
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=4D9F2462.60600@gmail.com \
--to=plyatov@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=chaoming_li@realsil.com.cn \
--cc=george0505@realtek.com \
--cc=johannes.berg@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).