From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: linux-wireless <linux-wireless@vger.kernel.org>,
"users@rt2x00.serialmonkey.com" <users@rt2x00.serialmonkey.com>,
fheinonen@gmail.com
Subject: Re: Zyxel NWD2705 testing
Date: Thu, 19 Sep 2013 15:21:04 +0200 [thread overview]
Message-ID: <523AFA40.3000503@gmail.com> (raw)
Felix Heinonen wrote:
> Hello, I have a Zyxel NWD2705 3x3 and according to my syslog based on
> rt3593 (0x0586, 0x3421). It is erroneously listed as rt3573 in the latest
> backports dev release. Is there a way I could help testing the rt3593
> chipset?
RT3573 and RT3593 devices are identified as 3593 because they use
the same chip.
But RT3573 brings a USB interface. And RT3593 is PCIe, still unsupported
by rt2x00.
next reply other threads:[~2013-09-19 13:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 13:21 Xose Vazquez Perez [this message]
[not found] ` <CALcAVvn9tkDGYxw8eEZszmEj94wNhYH1oG8zaFYNVu1VvjHWLg@mail.gmail.com>
2013-09-20 14:00 ` Zyxel NWD2705 testing 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=523AFA40.3000503@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=fheinonen@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).