From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com
Subject: Re: [PATCH] rt2800usb: Add three new USB IDs
Date: Tue, 12 Apr 2011 21:24:08 +0200 [thread overview]
Message-ID: <4DA4A6D8.2000806@gmail.com> (raw)
In-Reply-To: <4DA462F0.6090105@lwfinger.net>
On 04/12/2011 04:34 PM, Larry Finger wrote:
> Kill the patch. It appears these are phantom devices, or their original
> inclusion was a mistake.
More ids. But no time for a patch, sorry.
missing, taken from ralink windows driver. And the identified ones come
from ralink linux drivers:
0x04bb,0x094b I-O
0x050d,0x1003 Belkin
0x0586,0x343e RT3070 Zyxel
0x0789,0x0168 Logitec
0x0789,0x0169 Logitec
0x07b8,0x3073 AboCom
0x07b8,0x3074 AboCom
0x08b9,0x1197 RadioShack
0x0b05,0x166a PEGATRON
0x0b05,0x179d ASUS
0x0df6,0x003c Sitecom
0x0df6,0x004a Sitecom
0x0df6,0x004d Sitecom
0x0df6,0x0051 Sitecom
0x0df6,0x0053 Sitecom
0x0df6,0x005f RT3070 Sitecom 3072
0x0df6,0x0060 Sitecom
0x0df6,0x0062 Sitecom
0x13d3,0x3329 AzureWave
0x13d3,0x3365 RT5370 Azurewave
0x148f,0x3573 Ralink
0x148f,0x5370 RT5370 Ralink 5370
0x148f,0x5372 RT5370 Ralink 5370
0x148f,0xf101 Huawei
0x1eda,0x2012 RT3070 Airties
0x2001,0x3c17 Alpha
0x7392,0x7722 Edimax
already at rt2800usb.c, identified from ralink RT3070_RT3370 linux
driver. I believe 8070 == RT33XX :-?
0x07d1,0x3c17 D-Link 8070
0x7392,0x4085 2L Central Europe BV 8070
0x2019,0x5201 Planex Communications, Inc. RT8070
next prev parent reply other threads:[~2011-04-12 19:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-10 17:12 [PATCH] rt2800usb: Add three new USB IDs Xose Vazquez Perez
2011-04-11 17:58 ` John W. Linville
2011-04-12 11:53 ` Xose Vazquez Perez
2011-04-12 13:19 ` Gertjan van Wingerde
2011-04-12 14:34 ` Larry Finger
2011-04-12 19:24 ` Xose Vazquez Perez [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-04-08 14:23 Larry Finger
2011-04-08 14:24 ` Ivo Van Doorn
2011-04-08 14:33 ` Gertjan van Wingerde
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=4DA4A6D8.2000806@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=users@rt2x00.serialmonkey.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).