From patchwork Sun Aug 26 13:33:29 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Maximilian Engelhardt X-Patchwork-Id: 1375281 Return-Path: X-Original-To: patchwork-linux-wireless@patchwork.kernel.org Delivered-To: patchwork-process-083081@patchwork2.kernel.org Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by patchwork2.kernel.org (Postfix) with ESMTP id C930DDFABE for ; Sun, 26 Aug 2012 14:11:39 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753669Ab2HZNoP (ORCPT ); Sun, 26 Aug 2012 09:44:15 -0400 Received: from daemonizer.de ([178.77.99.65]:38536 "EHLO daemonizer.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752300Ab2HZNoF (ORCPT ); Sun, 26 Aug 2012 09:44:05 -0400 X-Greylist: delayed 626 seconds by postgrey-1.27 at vger.kernel.org; Sun, 26 Aug 2012 09:44:05 EDT Received: from eisbaer.localnet (unknown [IPv6:2001:4ca0:200:3:0:5efe:a96:5621]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by daemonizer.de (Postfix) with ESMTPSA id 6538511DC00BC; Sun, 26 Aug 2012 15:33:34 +0200 (CEST) From: Maximilian Engelhardt To: linux-wireless Cc: Roman Thiele Subject: Getting ASUS USB-N53 out of CONFIG_RT2800USB_UNKNOWN Date: Sun, 26 Aug 2012 15:33:29 +0200 Message-ID: <17042485.dTE7gQicta@eisbaer> User-Agent: KMail/4.8.4 (Linux/3.2.0-3-rt-amd64; KDE/4.8.4; x86_64; ; ) MIME-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org Hallo, I recently bought an Asus USB-N53 Dual Band Wireless Network Adapter and noticed that I have to enable CONFIG_RT2800USB_UNKNOWN to get it working. With this option enabled everything is working fine as far as I have tested. So I'd line to get things right and move this device out of CONFIG_RT2800USB_UNKNOWN to where it belongs. Here is the information I have about this device, feel tree to ask if you need anything addition. Asus Website about the device: http://www.asus.com/Networks/Wireless_Adapters/USBN53/ output of lsusb: Bus 005 Device 013: ID 0b05:179d ASUSTek Computer, Inc. USB-N53 802.11abgn Network Adapter [Ralink RT3572] output of dmesg: usb 5-6: new high-speed USB device number 13 using ehci_hcd usb 5-6: New USB device found, idVendor=0b05, idProduct=179d usb 5-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 5-6: Product: 802.11 n WLAN usb 5-6: Manufacturer: Ralink usb 5-6: SerialNumber: 1.0 usb 5-6: reset high-speed USB device number 13 using ehci_hcd ieee80211 phy6: Selected rate control algorithm 'minstrel_ht' Registered led device: rt2800usb-phy6::radio Registered led device: rt2800usb-phy6::assoc Registered led device: rt2800usb-phy6::quality So according to lsusb this is a RT3572 device, which does also match with the chip description from ralink: http://www.ralinktech.com/en/02_products/product.php?sn=1009 I suggest moving the device to the CONFIG_RT2800USB_RT35XX section in rt2800usb.c, see attached patch. Greeting, Maxi Signed-off-by: Maximilian Engelhardt diff --git a/drivers/net/wireless/rt2x00/rt2800usb.c b/drivers/net/wireless/rt2x00/rt2800usb.c index 6cf3365..6681bfc 100644 --- a/drivers/net/wireless/rt2x00/rt2800usb.c +++ b/drivers/net/wireless/rt2x00/rt2800usb.c @@ -1157,6 +1157,8 @@ static struct usb_device_id rt2800usb_device_table[] = { { USB_DEVICE(0x1690, 0x0744) }, { USB_DEVICE(0x1690, 0x0761) }, { USB_DEVICE(0x1690, 0x0764) }, + /* ASUS */ + { USB_DEVICE(0x0b05, 0x179d) }, /* Cisco */ { USB_DEVICE(0x167b, 0x4001) }, /* EnGenius */ @@ -1222,7 +1224,6 @@ static struct usb_device_id rt2800usb_device_table[] = { { USB_DEVICE(0x0b05, 0x1760) }, { USB_DEVICE(0x0b05, 0x1761) }, { USB_DEVICE(0x0b05, 0x1790) }, - { USB_DEVICE(0x0b05, 0x179d) }, /* AzureWave */ { USB_DEVICE(0x13d3, 0x3262) }, { USB_DEVICE(0x13d3, 0x3284) },