linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Helmut Schaa <helmut.schaa@googlemail.com>
To: Johannes Stezenbach <js@sig21.net>
Cc: Juan Carlos Garza <juancarlosgarza@gmail.com>,
	users@rt2x00.serialmonkey.com, linux-wireless@vger.kernel.org
Subject: Re: [rt2x00-users] rt2800usb stops working with big file transfers in AP and IBSS
Date: Fri, 18 Mar 2011 19:05:31 +0100	[thread overview]
Message-ID: <201103181905.32058.helmut.schaa@googlemail.com> (raw)
In-Reply-To: <20110318171222.GB12889@sig21.net>

Hi Johannes,

Am Freitag, 18. März 2011 schrieb Johannes Stezenbach:
> On Fri, Mar 18, 2011 at 04:23:15PM +0100, Juan Carlos Garza wrote:
> > I applied the patches (manually), and tested the stick.
> > 
> > The transfer of big loads now is successful. The
> > "rt2800_txdone_entry_check:" warnings are still there, but they are
> > less frequent (just like in the example i gave you with the laptop
> > where it succeeded with the unpatched driver), some 5 warnings every
> > 1, 2 or 3 seconds.
> 
> Thanks for testing!  The occational "tx status missed" is unavoidable
> due to hardware limitations.  My patches reduce the number of them,
> but more importantly they fix a few issues with TX (status) timeout handling.
> (IIRC false positives in TX timeout check, and fluash would wait for
> TX queue empty which would never happen without the timer to reap
> the status queue.)
> 
> I tested a lot with these patches and they work stable for me, however I
> must admit I'm not sure why they help in your case (i.e. why does
> bulk transfer stall without these patches?).

Just an assumption: In rt2800pci I had the problem that the tx status register
sometimes suffered from overflows. And I was able to avoid the overflow by
reading the TX_STA_FIFO register fast enough (in hard irq context).

And I guess your patch also changed the timing of TX_STA_FIFO reads is
rt2800usb and thus reduces the number of overflows.

However, this is just a shot in the dark.

Helmut

      reply	other threads:[~2011-03-18 18:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-16 15:24 rt2800usb stops working with big file transfers in AP and IBSS Juan Carlos Garza
2011-03-16 17:24 ` Walter Goldens
2011-03-17 12:16 ` [rt2x00-users] " Helmut Schaa
2011-03-17 17:01   ` Juan Carlos Garza
2011-03-17 20:07     ` Helmut Schaa
2011-03-18 15:23       ` Juan Carlos Garza
2011-03-18 15:42         ` Helmut Schaa
2011-03-18 16:15           ` Ivo Van Doorn
2011-03-18 16:56             ` Johannes Stezenbach
2011-03-18 17:24               ` Juan Carlos Garza
2011-03-18 19:13                 ` Johannes Stezenbach
2011-03-21 14:31                   ` Juan Carlos Garza
2011-03-18 17:12         ` Johannes Stezenbach
2011-03-18 18:05           ` 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=201103181905.32058.helmut.schaa@googlemail.com \
    --to=helmut.schaa@googlemail.com \
    --cc=js@sig21.net \
    --cc=juancarlosgarza@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).