From: Hans de Goede <hdegoede@redhat.com>
To: Arend van Spriel <arend@broadcom.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
Subject: Re: [linux-sunxi] Firmware for Bluetooth (and wifi)
Date: Sun, 26 Jan 2014 14:19:53 +0100 [thread overview]
Message-ID: <52E50B79.9080909@redhat.com> (raw)
In-Reply-To: <52E50683.8060003@broadcom.com>
Hi,
On 01/26/2014 01:58 PM, Arend van Spriel wrote:
> On 01/26/2014 11:23 AM, Hans de Goede wrote:
>> Hi,
>>
>> On 01/26/2014 09:53 AM, Arend van Spriel wrote:
>>> 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:
>>>
>>> Bedankt, Hans
>>>
>>> Looking at the log it looks more or less ok. wpa_supplicant (assume you
>>> use that) first does three regular scans which end with no APs found.
>>> Not sure why that happens unless you are in a shielded room :-) After
>>> those scans wpa_supplicant tries to tell the device to do a so-called
>>> scheduled scan. Basically, it is a scan offload. However, the driver
>>> still thinks there is a regular scan ongoing. This needs to be
>>> investigated more.
>>
>> Thanks for looking into this. I've nothing scheduled this entire Sunday
>> except working on hobby projects. If there is anything I can do to help,
>> you can find me in #linux-sunxi on freenode irc. My nick is hansg.
>>
>> I would really like to get this working, so feel free to poke me to run
>> any tests / debug log gathering exercises you think will be helpful.
>
> I did a quick diff between your brcmfmac folder and mine. I am curious
> what your results are after the merge window. There has been a lot of
> rework in SDIO part of brcmfmac driver.
Ok, I plan to rebase my tree on 3.14-rc1 when it is released. I'll run
some more tests then and let you know how things go.
Regards,
Hans
next prev parent reply other threads:[~2014-01-26 13:21 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 [this message]
2014-01-26 12:07 ` Hans de Goede
2014-01-26 15:49 ` Hans de Goede
2014-01-26 11:04 ` Arend van Spriel
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=52E50B79.9080909@redhat.com \
--to=hdegoede@redhat.com \
--cc=arend@broadcom.com \
--cc=benn@cubietech.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).