From: Hauke Mehrtens <hauke@hauke-m.de>
To: Arend van Spriel <arend@broadcom.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 00/19] brcmsmac: use sprom and PCIe code from bcma
Date: Mon, 30 Apr 2012 00:45:41 +0200 [thread overview]
Message-ID: <4F9DC495.7060103@hauke-m.de> (raw)
In-Reply-To: <4F9D7032.40507@broadcom.com>
On 04/29/2012 06:45 PM, Arend van Spriel wrote:
> On 04/29/2012 03:21 PM, Hauke Mehrtens wrote:
>> On 04/29/2012 10:13 AM, Arend van Spriel wrote:
>>> On 04/29/2012 02:50 AM, Hauke Mehrtens wrote:
>>>> I have not completely runtime tested these patches as I do not have a
>>>> PCI(e) devices currently supported by brcmsmac. My SoC (BCM4718) and
>>>> the PCI devices connected to my SoC (BCM43224) are currently not
>>>> working with brcmsmac, but they are failing much later that without
>>>> these patches.
>>>
>>> I will test this patch series as well on PCI(e) devices. So you do have
>>> a bcm43224 card, but no laptop to fit it in? Just wondering. I will send
>>> the results.
>>>
>>> Gr. AvS
>>>
>> Hi Arend,
>>
>> Thanks for testing these patches. My bcm43224 is directly soldered on
>> the main board where also the bcm4718 is on, there is no connector or
>> something like that between the bcm4718 and the bcm43224, it is
>> impossible to remove the bcm43224 and plug it into a laptop. The bcm4718
>> has some problems with the PCIe bus see comment on bcma_wflush16() in
>> drivers/net/wireless/brcm80211/brcmsmac/dma.h.
>
> I see. I have a bcm4718 with a mini-PCIe connector so I assumed that was
> the same for you.
Yes looks like that, you should try it out with brcmsmac. ;-)
>
>> I now finally got the bcm43224 a little bit working, I was able to scan
>> for networks, but I was unable to connect to one, I just saw 2 networks
>> form devices on my desk, not the other ~15 my Intel card sees. The
>> bcm43224 should just be used for 5GHz on my device and the sprom is also
>> just configuration for 5GHz operation and I have only some 2.4 GHz
>> access points laying around here, so that could be the problem.
>>
>> The Wifi of the bcm4718 is still not working for me. The wifi core has a
>> core rev of 17, I handled it the same as core rev 23, but I am getting
>> the following errors and after that the system freezes.
>>
>> [ 80.232000] ieee80211 phy1: wl1: wlc_coreinit: ucode did not
>> self-suspend!
The problem is here, the rest are just other problems because of this.
The driver should abort the initialization at this point.
The ucode does not start after it was loaded onto the device in
brcms_ucode_download(). I never had such problems when using b43.
>> [ 80.240000] ieee80211 phy1: wlc_coreinit: txfifo mismatch: ucode size
>> 111 driver size 28518 index 5
>> [ 80.380000] ieee80211 phy1: wl1: wlc_suspend_mac_and_wait: waited
>> 83000 uS and MI_MACSSPNDD is still not on.
>
> In several scenarios the driver puts the d11core in suspended state.
> This message indicates d11core does not end up in suspended state.
> Normally, means the d11core got stuck. The two messages before that look
> interesting.
>
>> [ 80.388000] ieee80211 phy1: wl1: psmdebug 0x00ff8cd4, phydebug
>> 0x00000000, psm_brc 0x0000
>
> The psmdebug register is the same in all the messages, which confirms
> the d11core is stuck.
>
>> ... (~6 times the same 2 lines)
>> [ 81.132000] ieee80211 phy1: wl1: wlc_suspend_mac_and_wait: waited
>> 83000 uS and MI_MACSSPNDD is still not on.
>> [ 81.144000] ieee80211 phy1: wl1: psmdebug 0x00ff8cd4, phydebug
>> 0x00000000, psm_brc 0x0000
>> [ 81.156000] ieee80211 phy1: brcms_ops_bss_info_changed: qos enabled:
>> false (implement)
>> [ 81.164000] ieee80211 phy1: brcms_ops_config: change power-save mode:
>> false (implement)
>> [ 81.256000] ieee80211 phy1: wl1: wlc_suspend_mac_and_wait: waited
>> 83000 uS and MI_MACSSPNDD is still not on.
>> [ 81.268000] ieee80211 phy1: wl1: psmdebug 0x00ff8cd4, phydebug
>> 0x00000000, psm_brc 0x0000
>> ... (~3 times the same 2 lines)
>> [ 81.708000] ieee80211 phy1: wl1: wlc_suspend_mac_and_wait: waited
>> 83000 uS and MI_MACSSPNDD is still not on.
>> [ 81.720000] ieee80211 phy1: wl1: psmdebug 0x00ff8cd4, phydebug
>> 0x00000000, psm_brc 0x0000
>> [ 81.732000] ieee80211 phy1: wl1: fifo 0: descriptor error
>> [ 81.736000] ieee80211 phy1: wl1: fatal error, reinitializing
>
> This descriptor error should re-initialize the driver, but there are
> already problems reported about that last resort.
>
>> b43 is working in access pint mode with the wifi core of the bcm4718.
>
> I like pints ;-) brcmsmac currently only supports STA mode.
>
> What firmware are you using?
On b43 I am using firmware version 666.2 from wl 5.100.138, but also
older versions are working. On brcmsmac I am using bcm43xx-0.fw and
bcm43xx_hdr-0.fw from the linux-firmware git repo.
Does the ucode you provide in bcm43xx-0.fw and bcm43xx_hdr-0.fw support
rev 17 ieee80211 cores? For b43 it is the same file for all n-phy based
cores rev >= 16, so for wl it should be the same, but have you added
some special handling into this firmware for brcmsmac?
Hauke
next prev parent reply other threads:[~2012-04-29 22:45 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-29 0:50 [PATCH 00/19] brcmsmac: use sprom and PCIe code from bcma Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 01/19] brcmsmac: use sprom " Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 02/19] brcmsmac: remove brcmsmac own sprom parsing Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 03/19] brcmsmac: get board and chip info from bcma Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 04/19] brcmsmac: remove support for cc rev < 20 Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 05/19] brcmsmac: remove references to PCI Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 06/19] brcmsmac: remove PCIe functions needed for PCIe core rev <= 10 Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 07/19] brcmsmac: remove pcicore_hwup() Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 08/19] brcmsmac: remove ai_pci_setup() Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 09/19] brcmsmac: remove ai_chipcontrl_epa4331 Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 10/19] brcmsmac: remove ai_gpiocontrol() Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 11/19] brcmsmac: remove _ai_clkctl_cc() Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 12/19] brcmsmac: remove pcicore_attach() Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 13/19] brcmsmac: remove pcicore_find_pci_capability() Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 14/19] brcmsmac: remove pcie_extendL1timer() Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 15/19] brcmsmac: remove pcicore_fixcfg() Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 16/19] brcmsmac: remove nicpci.c Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 17/19] brcmsmac: do not access host_pci Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 18/19] brcmsmac: read PCI vendor and device id only for PCI devices Hauke Mehrtens
2012-04-29 0:50 ` [PATCH 19/19] brcmsmac: handle non pci in ai_deviceremoved() Hauke Mehrtens
2012-04-29 8:13 ` [PATCH 00/19] brcmsmac: use sprom and PCIe code from bcma Arend van Spriel
2012-04-29 13:21 ` Hauke Mehrtens
2012-04-29 16:45 ` Arend van Spriel
2012-04-29 22:45 ` Hauke Mehrtens [this message]
2012-05-01 9:35 ` Arend van Spriel
2012-05-01 18:21 ` Hauke Mehrtens
2012-06-02 14:21 ` Hauke Mehrtens
2012-05-02 6:06 ` Arend van Spriel
2012-05-02 22:34 ` Hauke Mehrtens
2012-05-03 6:13 ` Arend van Spriel
2012-05-03 6:18 ` Arend van Spriel
2012-05-03 11:46 ` Hauke Mehrtens
2012-05-08 12:39 ` Arend van Spriel
2012-05-09 9:00 ` Hauke Mehrtens
2012-05-09 9:26 ` Arend van Spriel
2012-05-09 22:27 ` Hauke Mehrtens
2012-05-10 12:14 ` 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=4F9DC495.7060103@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=arend@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 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.