From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>,
linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com
Subject: Re: Questions about rt2800usb
Date: Sun, 10 Apr 2011 18:55:57 +0200 [thread overview]
Message-ID: <4DA1E11D.6060703@gmail.com> (raw)
Larry Finger wrote:
> I noticed that rt2870sta includes a few USB IDs not found in rt2800usb, namely:
>
> 0x2001:0x3c09, 0x2001:0x3c0a, and 0x2019:0xed14.
>
> Any reasons why these should not be included in rt2800usb?
They were in the ralink driver imported into the kernel,
and later they were eliminated in recent versions of ralink drivers:
2010_0709_RT2870_Linux_STA_v2.4.0.1
2010_1215_RT3572_Linux_STA_v2.5.0.0.DPO
2011_0107_RT3070_RT3370_Linux_STA_v2.5.0.1_DPO
Only these four were meaningful, and they were included by me in rt2800usb.c:
<http://marc.info/?l=linux-wireless&m=130125079513964&w=2>
0x0411,0x016f de37cd49b5a54facef174cf34496919857436e8f MelCo(Buffalo) WLI-UC-G301N
0x050d,0x825b 12840c63b0679f7fab88ea1cc26b52db8b574ce7 Belkin F5D8055
0x050d,0x935a 705059a670f3af2b37695e82de0ee58e75e656ed Belkin F6D4050 v1
0x050d,0x935b 5d92fe3387d086fc2f10426fbdb6b86d6cce5a47 Belkin F6D4050 v2
I think 0x2001:0x3c09, 0x2001:0x3c0a, and 0x2019:0xed14 can be despised,
unless they also be in the windows driver.
next reply other threads:[~2011-04-10 16:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-10 16:55 Xose Vazquez Perez [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-04-07 21:49 Questions about rt2800usb Larry Finger
2011-04-07 22:19 ` Walter Goldens
2011-04-07 23:03 ` Steev Klimaszewski
2011-04-08 9:32 ` Walter Goldens
2011-04-08 9:42 ` Ivo Van Doorn
2011-04-08 9:54 ` Walter Goldens
2011-04-08 12:21 ` Walter Goldens
2011-04-08 12:41 ` Helmut Schaa
2011-04-08 16:31 ` Walter Goldens
2011-04-08 6:50 ` Helmut Schaa
2011-04-08 7:42 ` Ivo Van Doorn
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=4DA1E11D.6060703@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).