From: Arend van Spriel <arend@broadcom.com>
To: Hans de Goede <hdegoede@redhat.com>, <linux-sunxi@googlegroups.com>
Cc: Julian Calaby <julian.calaby@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Olliver Schinagl <oliver+list@schinagl.nl>, <benn@cubietech.com>,
brcm80211-dev-list <brcm80211-dev-list@broadcom.com>
Subject: Re: [linux-sunxi] Firmware for Bluetooth (and wifi)
Date: Sun, 26 Jan 2014 12:04:10 +0100 [thread overview]
Message-ID: <52E4EBAA.2010204@broadcom.com> (raw)
In-Reply-To: <52E29607.8040102@redhat.com>
On 01/24/2014 05:34 PM, Hans de Goede wrote:
> Hi,
>
> On 01/24/2014 11:25 AM, Arend van Spriel wrote:
>> On 01/23/2014 11:39 PM, Hans de Goede wrote:
>>> Hi,
>>>
>>> I've been working on updating sunxi-devel to include more
>>> recent versions if your gmac patches, as well as adding support
>>> for the wifi + bluetooth found on the cubietruck.
>>>
>>> Here is my current work on this:
>>>
>>> https://github.com/jwrdegoede/linux-sunxi/commits/sunxi-devel
>>>
>>> It is close to working, but unfortunately it does not work,
>>> here is what I get in dmesg when I modprove the module:
>>>
>>> [ 99.700889] brcmfmac_sdio mmc1:0001:1: device tree node not found
>>> [ 100.020984] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0:
>>> Apr 22 2013 14:50:00 version 5.90.195.89.6 FWID 01-b30a427d
>>> [ 100.260948] brcmfmac: brcmf_fil_cmd_data: Failed err=-23
>>> [ 100.281260] brcmfmac: brcmf_fil_cmd_data: Failed err=-23
>>> [ 100.322508] usbcore: registered new interface driver brcmfmac
>>> [ 160.445215] brcmfmac: brcmf_cfg80211_sched_scan_start: Scanning
>>> already: status (1)
>>> [ 203.445404] brcmfmac: brcmf_cfg80211_sched_scan_start: Scanning
>>> already: status (1)
>>> [ 256.445140] brcmfmac: brcmf_cfg80211_sched_scan_start: Scanning
>>> already: status (1)
>>
>> Can you enable debug logging in brcmfmac, ie. debug=0xd416 so I can have
>> a look.
>
> I've captured a log with these flags until the first "Scanning already"
> message, you can find it here:
Hi Hans,
The log looks confusing.
[ 543.512827] brcmfmac: brcmf_fweh_event_worker event ESCAN_RESULT (69)
ifidx 0 bsscfg 0 addr 02:00:00:00:00:00
[ 543.512840] brcmfmac: brcmf_fweh_event_worker version 2 flags 0
status 0 reason 0
[ 543.512849] brcmutil: event payload, len=12
[ 543.512860] 00000000: 0c 00 00 00 6d 00 00 00 34 12 00 00
....m...4...
[ 543.512872] brcmfmac: brcmf_inform_bss scanned AP count (0)
[ 543.512880] brcmfmac: brcmf_notify_escan_complete Enter
[ 543.512891] brcmfmac: brcmf_notify_escan_complete ESCAN Completed
scan: Done
[ 543.512911] brcmfmac: brcmf_fil_iovar_data_set name=mpc, len=4
[ 543.512919] brcmutil: data
[ 543.512928] 00000000: 01 00 00 00
....
[ 543.512941] brcmfmac: brcmf_sdbrcm_bus_txctl Enter
[ 543.512951] brcmfmac: brcmf_sdbrcm_bus_sleep Enter
[ 543.513018] brcmfmac: brcmf_sdbrcm_bus_rxctl Enter
The trace messages above indicate completion of regular scan and after
that the code does:
if (!test_and_clear_bit(BRCMF_SCAN_STATUS_BUSY, &cfg->scan_status))
brcmf_dbg(SCAN, "Scan complete, probably P2P scan\n");
[ 543.514758] brcmfmac: brcmf_cfg80211_sched_scan_start Enter
n_match_sets:0 n_ssids:0
[ 543.514777] brcmfmac: brcmf_cfg80211_sched_scan_start: Scanning
already: status (1)
So the bit SCAN_STATUS_BUSY should be cleared, but you get this message.
That makes no sense to me or test_and_clear_bit() does something else
than I expect. Either way the scheduled scan request would be rejected
because it has 0 match_sets and ssids. Maybe this is intended to
indicate any AP is to be reported. Will look in cfg80211 whether that is
the case.
Regards,
Arend
next prev parent reply other threads:[~2014-01-26 11:04 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52A040CE.5040706@schinagl.nl>
[not found] ` <CAFXj5xjJ0DTa0Qo1avLboQF-e3TFv3aEr_jjkuZjinwuTzXykQ@mail.gmail.com>
[not found] ` <52A09B5B.70800@schinagl.nl>
2013-12-05 21:46 ` [linux-sunxi] Firmware for Bluetooth (and wifi) Julian Calaby
2013-12-06 9:00 ` Arend van Spriel
2013-12-18 10:31 ` Arend van Spriel
2013-12-18 13:12 ` Hans de Goede
2013-12-18 16:16 ` Arend van Spriel
2013-12-18 16:39 ` Chen-Yu Tsai
2013-12-19 10:12 ` Chen-Yu Tsai
2013-12-26 16:13 ` Chen-Yu Tsai
2013-12-26 20:29 ` Hans de Goede
2013-12-27 11:47 ` Arend van Spriel
2013-12-27 12:36 ` Chen-Yu Tsai
2014-01-02 13:59 ` Arend van Spriel
2014-01-02 17:09 ` Chen-Yu Tsai
[not found] ` <5ce9ab14-5794-4c0d-a859-7a158655f58e@googlegroups.com>
2014-01-02 19:26 ` Michal Suchanek
2014-01-02 20:29 ` Arend van Spriel
2014-01-02 21:03 ` Arend van Spriel
2014-01-03 3:02 ` Chen-Yu Tsai
2014-01-08 8:56 ` Arend van Spriel
2014-01-08 9:23 ` Chen-Yu Tsai
2014-01-08 9:33 ` Arend van Spriel
2014-01-08 10:17 ` Chen-Yu Tsai
2014-01-23 22:39 ` Hans de Goede
2014-01-24 10:25 ` Arend van Spriel
2014-01-24 16:34 ` Hans de Goede
2014-01-26 8:53 ` Arend van Spriel
2014-01-26 8:56 ` Arend van Spriel
2014-01-26 10:23 ` Hans de Goede
2014-01-26 12:58 ` Arend van Spriel
2014-01-26 13:19 ` Hans de Goede
2014-01-26 12:07 ` Hans de Goede
2014-01-26 15:49 ` Hans de Goede
2014-01-26 11:04 ` Arend van Spriel [this message]
2014-01-26 12:09 ` Hans de Goede
2014-01-26 12:50 ` Arend van Spriel
2014-01-02 16:52 ` Michal Suchanek
2014-01-02 17:11 ` Chen-Yu Tsai
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=52E4EBAA.2010204@broadcom.com \
--to=arend@broadcom.com \
--cc=benn@cubietech.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=hdegoede@redhat.com \
--cc=julian.calaby@gmail.com \
--cc=linux-sunxi@googlegroups.com \
--cc=linux-wireless@vger.kernel.org \
--cc=oliver+list@schinagl.nl \
/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).