From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: users@rt2x00.serialmonkey.com, linux-wireless@vger.kernel.org
Subject: rt2x00: missing devices/chips
Date: Tue, 22 May 2012 22:35:27 +0200 [thread overview]
Message-ID: <4FBBF88F.5060508@gmail.com> (raw)
David Miller wrote:
> Xose Vazquez Perez (4):
> wireless: rt2x00: rt2800pci add more RT539x ids
> wireless: rt2x00: rt2800usb add more devices ids
> wireless: rt2x00: rt2800usb more devices were identified
Those were my final patches, from now on MediaTek Inc. guys
should take over it.
These are pending:
- RT3573:
0x1875,0x7733 RT3573 Air Live
0x7392,0x7733 RT3573 Edimax
0x0e66,0x0021 RT3573 Hawking
0x2019,0xed19 RT3573 Planex
0x148f,0x3573 RT3573 Ralink
0x0df6,0x0067 RT3573 Sitecom
- RT5572:
0x148f,0x5572 RT5572 Ralink
0x043e,0x7a32 RT5572 Arcadyan
0x2001,0x3c1a RT5572 D-Link DWA-160-B2
- Identify all UNKNOWN devices in rt2800usb.c
- There is also a handful of them(rt2800{usb,pci}) inside
the inf file of the Windows drivers missing.
next reply other threads:[~2012-05-22 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 20:35 Xose Vazquez Perez [this message]
2012-05-23 11:35 ` [rt2x00-users] rt2x00: missing devices/chips Helmut Schaa
2012-06-11 22:09 ` Xose Vazquez Perez
2012-06-11 22:59 ` Xose Vazquez Perez
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=4FBBF88F.5060508@gmail.com \
--to=xose.vazquez@gmail.com \
--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).