Message-ID: <4D9F2DEA.9080200@lwfinger.net>
Date: Fri, 08 Apr 2011 10:46:50 -0500
From: Larry Finger <Larry.Finger@lwfinger.net>
MIME-Version: 1.0
To: Igor Plyatov <plyatov@gmail.com>
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
References: <4D9F0DAE.30809@gmail.com> <4D9F14FE.8060905@lwfinger.net> <4D9F2462.60600@gmail.com>
In-Reply-To: <4D9F2462.60600@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Sender: linux-wireless-owner@vger.kernel.org

On 04/08/2011 10:06 AM, Igor Plyatov wrote:
> 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?

For my DWA-130, lsusb outputs the following

Bus 001 Device 003: ID 07d1:3300 D-Link System DWA-130 802.11n Wireless N 
Adapter(rev.E) [Realtek RTL8192SU]

The descriptive info is in file /usr/share/usb.ids and available on-line at 
http://www.linux-usb.org/usb.ids.

Larry