From: Helmut Schaa <helmut.schaa@googlemail.com>
To: Andreas Hartmann <andihartmann@freenet.de>
Cc: users@rt2x00.serialmonkey.com,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Re: Try to narrow down the problem with rt2800usb and rt3572 based USB WLAN devices
Date: Thu, 17 Nov 2011 20:20:13 +0100 [thread overview]
Message-ID: <4540730.yCbFJVVBHk@helmutmobil.site> (raw)
In-Reply-To: <4EC15D4F.1010207@dualc.maya.org>
Am Montag, 14. November 2011, 19:26:23 schrieb Andreas Hartmann:
> Hello Helmut,
>
> Helmut Schaa schrieb:
> > On Sat, Nov 12, 2011 at 6:00 PM, Andreas Hartmann
> > <andihartmann@01019freenet.de> wrote:
> >> Could anybody please try to explain this behavior, or even better, fix
> >> it (it looks really broken to me)?
> >
> > AFAIK it is possible to aggregate multiple frames into one URB
> > for rt2800 USB devices. However, rt2800usb doesn't make use
> > of this yet while the legacy driver does.
>
> Hmm, could this be the reason, why the device gets extremely hot during
> operation, especially when used in monitor mode (with airmon-ng)?
Interesting, maybe this is related, yes. Not sure though.
> Oh, I just remember, that during my "seven more packets" sniffing, the
> monitor mode of this device stalled after a few minutes. Probably the
> same reason why it doesn't work very well (respectively stalls
> completely) during normal mode.
>
> One more thing:
> At the moment, the tcp data transfer stalls, no more usb packets can be
> seen ... .
>
> > However, I don't think that
> > this is the cause for the poor performance you see ...
>
> Is it normal, that the device gets fired up with submits without waiting
> for any answers? The usb handling with the legacy driver is absolutely
> regular (submit / complete / submit / complete), the handling with the
> rt2800usb driver just looks totally messy to me (the urb ids of the
> submit / completes don't fit any more, even the "complete" comes before
> the "submit" (see package 83056 and 83062) ?!).
Unfortunately I don't know the rt2800 USB code very well but the tx status
handling was changed some time ago to read the TX_STA_FIFO register
asynchronously ...
Helmut
>
> Thanks for your explanation,
> Andreas
prev parent reply other threads:[~2011-11-17 19:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-12 17:00 Try to narrow down the problem with rt2800usb and rt3572 based USB WLAN devices Andreas Hartmann
2011-11-14 15:08 ` Helmut Schaa
2011-11-14 18:26 ` Andreas Hartmann
2011-11-17 19:20 ` Helmut Schaa [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=4540730.yCbFJVVBHk@helmutmobil.site \
--to=helmut.schaa@googlemail.com \
--cc=andihartmann@freenet.de \
--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).