From: Seth Forshee <seth.forshee@canonical.com>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
linux-usb@vger.kernel.org, "Chen,
Stephen" <scchen@qca.qualcomm.com>,
linux-wireless@vger.kernel.org
Subject: Re: carl9170 A-MPDU transmit problem
Date: Mon, 25 Feb 2013 08:44:25 -0600 [thread overview]
Message-ID: <20130225144425.GB13296@thinkpad-t410> (raw)
In-Reply-To: <201302242330.56346.chunkeey@googlemail.com>
On Sun, Feb 24, 2013 at 11:30:56PM +0100, Christian Lamparter wrote:
> Did you plug the DWA-160 device into a USB 3.0 port on your ivy bridge
> system or does it react in the same way on the 'legacy' USB 2.0 ports as
> well [so we are not comparing xhci (Ivy Bridge) to ehci (Arrandale)]?
Those two machines only have USB 3.0 ports, but I did manage to find an
Ivy Bridge machine with both. On that machine I get a stable connection
on the USB 2.0 ports and a flaky connection on the USB 3.0 ports. I
didn't actually sniff the frames, but the behavior is consistent with
what I saw on the other machines.
Seth
prev parent reply other threads:[~2013-02-25 14:44 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
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 [this message]
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=20130225144425.GB13296@thinkpad-t410 \
--to=seth.forshee@canonical.com \
--cc=chunkeey@googlemail.com \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=scchen@qca.qualcomm.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