All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maximilian Engelhardt <maxi@daemonizer.de>
To: linux-wireless <linux-wireless@vger.kernel.org>
Cc: Roman Thiele <roman.thiele@stusta.mhn.de>
Subject: Getting ASUS USB-N53 out of CONFIG_RT2800USB_UNKNOWN
Date: Sun, 26 Aug 2012 15:33:29 +0200	[thread overview]
Message-ID: <17042485.dTE7gQicta@eisbaer> (raw)

[-- Attachment #1: Type: text/plain, Size: 2408 bytes --]

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.


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) },


Greeting,
Maxi

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2012-08-26 13:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-26 13:33 Maximilian Engelhardt [this message]
2012-08-26 19:21 ` Getting ASUS USB-N53 out of CONFIG_RT2800USB_UNKNOWN Gertjan van Wingerde
2012-08-26 19:30   ` Maximilian Engelhardt

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=17042485.dTE7gQicta@eisbaer \
    --to=maxi@daemonizer.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=roman.thiele@stusta.mhn.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.