All of lore.kernel.org
 help / color / mirror / Atom feed
From: wireless newbie <wnewbie72@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: RT5390 rev 0503 problems
Date: Mon, 6 May 2013 10:26:14 +0300	[thread overview]
Message-ID: <CAApCBGyGdj3mb=nPrNrXxX3d=xm-00kf6Em=Uid6v7N-kpcKfg@mail.gmail.com> (raw)

Hi,

Has anyone experience with Ralink RT5390 chip with revision 0503? I
have that chip on my wireless usb module (WPER-172gn). I'm able to use
only one antenna with it but it has very poor rx signal level that
way. Adding second antenna for testing purposes clearly improves rx
level but that is no option for me.

I noticed in the list that someone had same sort of problem with
rt5390 rev 1502. Problem was hardware antenna diversity that wasn't
handled properly on the driver. Driver patch was provided to fix that.
I applied those same changes for rev 0503 and that solved my rx level
problem too.

But still I'm not getting the performance that I would expect. I
compare this module to WPER-150gn that has Ralink rt3070 in it. I'm
using those modules in station mode, and connect them to same AP from
same physical location. With rt3070 I can have two video streams
smoothly running over that wi-fi link. But when I switch to rt5390 I
have lots of hang ups on those video streams. Wi-fi link doesn't go
down or anything like that but the user experience is much worse than
with rt3070.

What could be the problem? Is rt5390 well supported on rt2x00 driver?
Or could it be that this revision (0503) has some changes in it that
needs further changes to driver? If anyone has any ideas of what I
should check or test, please let me know.

             reply	other threads:[~2013-05-06  7:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-06  7:26 wireless newbie [this message]
2013-05-06 14:58 RT5390 rev 0503 problems Xose Vazquez Perez
2013-05-07  6:16 ` wireless newbie

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='CAApCBGyGdj3mb=nPrNrXxX3d=xm-00kf6Em=Uid6v7N-kpcKfg@mail.gmail.com' \
    --to=wnewbie72@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.