From: Larry Finger <Larry.Finger@lwfinger.net>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: chaoming_li@realsil.com.cn, linville@tuxdriver.com,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Brian Lilly <brian@crystalfontz.com>,
Brent-Crosby <brent@crystalfontz.com>, Jim Wall <jimwall@q.com>,
Thomas Petazzoni <thomas@free-electrons.com>
Subject: Re: RTL8192CU on ARM not working
Date: Thu, 27 Jun 2013 09:45:32 -0500 [thread overview]
Message-ID: <51CC500C.9050602@lwfinger.net> (raw)
In-Reply-To: <20130627081225.GJ5803@lukather>
On 06/27/2013 03:12 AM, Maxime Ripard wrote:
> Hi everyone,
>
> I'm currently trying to use a RTL8192CU on an ARM (Freescale imx28,
> armv5) platform, using 3.10-rc3.
>
> Trouble is, while the chip is correctly detected and you can use iw on it
> without any problem it seems, once you start an association to an access
> point, the association goes on, seems to associate, displaying a WARN()
> message [1] and then, after what looks like a random amount of time (could
> be right away, could be after a few minutes), deassociate [2].
>
> During the time where it's associated, we never seem to transmit any
> packets, while iw reports packets being sent, I guess we can assume that
> they are actually never transmitted as well [3].
>
> What seems odd to me as well is that the signal power reported for the access
> point is excessively high when using iw scan (10 dbm), and once connected, the
> signal strength is -64dbm, which makes quite a huge difference.
That warning is under discussion. See the thread entitled "rtl8192cu: slow path
warning" in the linux-wireless ML. I will add you to the Cc list on those messages.
You should switch to kernel 3.10-rc7. There are a lot of changes to rtl8192cu in
that version that are not in -rc3. Those updates mostly affect WPA and WEP
encryption.
I never take signal power values seriously. Just observe the comments scattered
throughout the code regarding them.
Larry
prev parent reply other threads:[~2013-06-27 14:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 8:12 RTL8192CU on ARM not working Maxime Ripard
2013-06-27 12:13 ` Richard Genoud
2013-06-28 13:40 ` Maxime Ripard
2013-06-27 14:45 ` Larry Finger [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=51CC500C.9050602@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=alexandre.belloni@free-electrons.com \
--cc=brent@crystalfontz.com \
--cc=brian@crystalfontz.com \
--cc=chaoming_li@realsil.com.cn \
--cc=jimwall@q.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=maxime.ripard@free-electrons.com \
--cc=netdev@vger.kernel.org \
--cc=thomas@free-electrons.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).