From: Arend van Spriel <arend@broadcom.com>
To: Steeve Morin <steeve.morin@gmail.com>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: brcmfmac + AP6120 (brcm43362) doesn't connect to WPA2 AP (unprotected ok)
Date: Mon, 9 Feb 2015 23:00:28 +0100 [thread overview]
Message-ID: <54D92DFC.1080604@broadcom.com> (raw)
In-Reply-To: <CAEZVCP4bNmfnHH=Ksi6wMQoqdZGbprUH5X_VA41GRf9=h2MT1A@mail.gmail.com>
On 02/09/15 18:57, Steeve Morin wrote:
> Hi linux-wireless,
>
> I'm running brcmfmac from backports-3.19-rc1-1 on linux 3.10. running
> on an arm Amlogic S805 (cortex-a5, arm7) board (CX-S859).
>
> I had to apply multiple custom patches [1]:
> - Make sure the wifi chip is on via custom GPIO [1]
> - Remove a problematic piece of code related to power manager (will
> look into it later) [1]
> - Mix the mmc->max_blk_count on the host (would cause a BUG_ON
> assertion later on) [2] [3]
>
> After that, I am able to modprobe brcmfmac see wlan0.
> The interface correctly scans for wifi aps, and I can connect to
> unprotected ones.
>
> It fails, however, to connect to WPA/WPA2 protected aps. I have
> attached a debug log obtained with debug=0xffffff [4]
> I don't see any errors in it though...
>
> Would anyone of you guys have any idea why ?
In the log I don't see any connect attempt. Only seeing a scan
completing. So how do you try to connect?
Regards,
Arend
> Thanks a lot,
>
> [1] https://gist.github.com/steeve/10a9a643476cea99abf4#file-backports-power-on-wifi-sdio-patch
> [2] https://gist.github.com/steeve/10a9a643476cea99abf4#file-fix-block-size-patch
> [3] https://github.com/codesnake/linux-amlogic/blob/master/drivers/amlogic/mmc/aml_sdio.c#L317
> [4] https://gist.github.com/steeve/10a9a643476cea99abf4#file-003-dmesg-log
next prev parent reply other threads:[~2015-02-09 22:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 17:57 brcmfmac + AP6120 (brcm43362) doesn't connect to WPA2 AP (unprotected ok) Steeve Morin
2015-02-09 22:00 ` Arend van Spriel [this message]
2015-02-09 22:17 ` Steeve Morin
2015-02-09 23:06 ` Steeve Morin
2015-02-10 0:34 ` Steeve Morin
2015-02-10 1:37 ` Steeve Morin
2015-02-10 17:31 ` Arend van Spriel
2015-02-10 20:03 ` Steeve Morin
2015-02-10 21:42 ` Arend van Spriel
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=54D92DFC.1080604@broadcom.com \
--to=arend@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=steeve.morin@gmail.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).