From: Andreas Hartmann <andihartmann@01019freenet.de>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com,
IvDoorn@gmail.com, linville@tuxdriver.com, gwingerde@gmail.com,
helmut.schaa@googlemail.com
Subject: Re: [rt2x00-users] [PATCH] wireless: rt2x00: rt2800usb add more devices ids
Date: Sun, 15 Apr 2012 08:37:42 +0200 [thread overview]
Message-ID: <4F8A6CB6.4080006@01019freenet.de> (raw)
In-Reply-To: <1334448592-16391-1-git-send-email-xose.vazquez@gmail.com>
Xose Vazquez Perez wrote:
> They were taken from ralink drivers:
> 2011_0719_RT3070_RT3370_RT5370_RT5372_Linux_STA_V2.5.0.3_DPO
> 2012_03_22_RT5572_Linux_STA_v2.6.0.0_DPO
>
> 0x1eda,0x2210 RT3070 Airties
>
> 0x083a,0xb511 RT3370 Panasonic
> 0x0471,0x20dd RT3370 Philips
>
> 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
> 0x1690,0x0764 RT35xx Askey
> 0x0df6,0x0065 RT35xx Sitecom
> 0x0df6,0x0066 RT35xx Sitecom
> 0x0df6,0x0068 RT35xx Sitecom
>
> 0x2001,0x3c1c RT5370 DLink
> 0x2001,0x3c1d RT5370 DLink
>
> 2001 is D-Link not Alpha
Did you test them? What did you test exactly? What exactly works, what
does not?
It doesn't mean anything, if they work with the legacy driver. Linksys
WUSB600Nv2 e.g. works fine with the legacy driver, but only limited (if
at all) with rt2800usb yet.
Regards,
Andreas
next prev parent reply other threads:[~2012-04-15 6:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-15 0:09 [PATCH] wireless: rt2x00: rt2800usb add more devices ids Xose Vazquez Perez
2012-04-15 6:37 ` Andreas Hartmann [this message]
2012-04-15 9:19 ` [rt2x00-users] " Xose Vazquez Perez
2012-04-15 12:03 ` Andreas Hartmann
2012-04-15 13:04 ` Gertjan van Wingerde
2012-04-15 18:09 ` Andreas Hartmann
2012-04-15 12:25 ` 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=4F8A6CB6.4080006@01019freenet.de \
--to=andihartmann@01019freenet.de \
--cc=IvDoorn@gmail.com \
--cc=gwingerde@gmail.com \
--cc=helmut.schaa@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=users@rt2x00.serialmonkey.com \
--cc=xose.vazquez@gmail.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).