From: Christian Lamparter <chunkeey@googlemail.com>
To: Seth Forshee <seth.forshee@canonical.com>
Cc: Sarah Sharp <sarah.a.sharp@linux.intel.com>,
Alan Stern <stern@rowland.harvard.edu>,
linux-wireless@vger.kernel.org,
USB list <linux-usb@vger.kernel.org>
Subject: Re: carl9170 A-MPDU transmit problem
Date: Mon, 25 Feb 2013 20:52:46 +0100 [thread overview]
Message-ID: <201302252052.47208.chunkeey@googlemail.com> (raw)
In-Reply-To: <20130225194623.GI13296@thinkpad-t410>
On Monday, February 25, 2013 08:46:23 PM Seth Forshee wrote:
> On Mon, Feb 25, 2013 at 11:13:57AM -0800, Sarah Sharp wrote:
> > Hmm, yeah, that kind of points to an Intel xHCI hardware issue. It's
> > too bad you don't have a USB analyzer (the high speed ones are about
> > $480). Can you send me a link so I can purchase the device and test it
> > with my analyzer?
>
> Hmm. This looks the same, but it sounds like there are multiple hardware
> versions sold under the same name so I'm not sure. The one I have is
> hardware version A2.
>
> http://www.amazon.com/D-Link-DWA-160-Extreme-N-Dual-Band-802-11n/dp/B00127OVHI
>
Or this one:
<http://www.ebay.com/itm/D-Link-DWA-160-300Mbps-Xtreme-N-Duo-Band-Wireless-USB-Adapter-Win7-Vista-XP-/180869622792>
In the description they say it's A2 (so it should be the same Seth is using)
(Note: The "current" DWA-160 have RaLink/MediaTek chips)
Regards,
Chr
next prev parent reply other threads:[~2013-02-25 19:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 20:50 carl9170 A-MPDU transmit problem Seth Forshee
2013-02-22 22:07 ` Christian Lamparter
2013-02-22 22:54 ` Seth Forshee
2013-02-22 23:48 ` Christian Lamparter
2013-02-23 6:46 ` Seth Forshee
2013-02-23 14:07 ` Christian Lamparter
2013-02-23 21:26 ` Alan Stern
2013-02-24 4:52 ` Seth Forshee
2013-02-24 15:54 ` Alan Stern
2013-02-24 22:30 ` Christian Lamparter
2013-02-24 23:41 ` Alan Stern
2013-02-25 14:51 ` Seth Forshee
2013-02-25 15:04 ` Christian Lamparter
2013-02-25 15:29 ` Alan Stern
2013-02-25 16:03 ` Christian Lamparter
2013-02-25 19:13 ` Sarah Sharp
2013-02-25 19:46 ` Seth Forshee
2013-02-25 19:52 ` Christian Lamparter [this message]
2013-02-25 20:19 ` Alan Stern
2013-02-25 23:30 ` Christian Lamparter
2013-02-26 16:50 ` Seth Forshee
2013-03-07 17:46 ` Seth Forshee
2013-03-07 23:37 ` Sarah Sharp
2013-02-25 22:42 ` Seth Forshee
2013-02-25 20:23 ` Seth Forshee
2013-02-25 14:44 ` Seth Forshee
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=201302252052.47208.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sarah.a.sharp@linux.intel.com \
--cc=seth.forshee@canonical.com \
--cc=stern@rowland.harvard.edu \
/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).