linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "Hauke Mehrtens" <hauke@hauke-m.de>,
	brcm80211-dev-list@broadcom.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 00/18] brcmsmac: update to get SoCs working
Date: Sun, 8 Jul 2012 21:10:39 +0200	[thread overview]
Message-ID: <4FF9DB2F.3080606@broadcom.com> (raw)
In-Reply-To: <20120706183547.GC2353@tuxdriver.com>

On 07/06/2012 08:35 PM, John W. Linville wrote:
> On Tue, Jul 03, 2012 at 09:13:13AM +0200, Arend van Spriel wrote:
>> On 06/30/2012 03:16 PM, Hauke Mehrtens wrote:
>>> This series contains some patches needed to get brcmsmac working on 
>>> SoCs like the BCM4718.
>>> The last part which adds core rev 17 (used in the BCM4718) to the list 
>>> of supported cores is missing, because we do not have a firmware 
>>> supporting this core yet, but I extended the b43 fwcutter to generate 
>>> a firmware which brcmsmac accepts. With this firmware my BCM4718 
>>> works. I would appreciate an official firmware release from Broadcom 
>>> adding support for this core.
>>> The final patch adding support for the BCM43224 is missing because 
>>> the PCIe host controller on the BCM4718 still causes problems and I 
>>> have to add some more read after writes into the code, for now it uses 
>>> an ugly hack and sometimes the problems still occur.
>>>
>>> The wifi is not stable on the BCM4718, I had no problems connecting to 
>>> my ath9k driven access point but I have problems connecting to my 
>>> BCM47186 based AP running the vendor firmware with the Broadcom 
>>> proprietary driver.
>>> I get 12MBit/s max with the BCM4718 connected to ath9k on the 2.4 GHz 
>>> band and 35 MBit/s max with the BCM43224 on the 5Ghz band connected to 
>>> a Broadcom based AP running the proprietary driver. This seams to be 
>>> CPU bounced as I have over 50% sirq in both cases.
>>>
>>> brcmsmac starts on the BCM47186 (id: 0x5357), but it does not tx or rx 
>>> any traffic.
>>>
>>> One patch extends the xmtfifo_sz array for more core revs, I just toke 
>>> the values from the other phy-n cores and hope this is correct.
>>>
>>> These patches are depending on: "[PATCH v2 0/9] bcma misc updates" and 
>>> based on wireless-testing.
>>>
>>> I will send a patch for bcma which converts the warning message when it 
>>> found a PCI and not a PCIe card into a WARN.
>>>
>>> v2:
>>>   - when something depends on a patch for bcma, which is not in 
>>>     wireless-testing yet, I add that to the commit comment.
>>>   - removed changes for BCM43421 and BCM6362 as I do not have a device
>>>     to test this.
>>>   - xmtfifo_sz now starts at core rev 17 and contains the correct values 
>>>     for core rev 28
>>>   - make brcms_c_chipmatch() also work for SoCs
>>>   - typos and format changes
>>>
>>
>> I have acked all patches, but would like to do some sanity testing today.
> 
> Have you had a chance to do this testing?  Are you OK with this series?
> 
> John
> 

Yes, I am. Sorry for not getting back on that earlier.

Gr. AvS



      reply	other threads:[~2012-07-08 19:10 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-30 13:16 [PATCH v2 00/18] brcmsmac: update to get SoCs working Hauke Mehrtens
2012-06-30 13:16 ` [PATCH v2 01/18] brcmsmac: remove PCIE() macro Hauke Mehrtens
2012-07-03  7:07   ` Arend van Spriel
2012-06-30 13:16 ` [PATCH v2 02/18] brcmsmac: remove PCI_FORCEHT() macro Hauke Mehrtens
2012-06-30 13:16 ` [PATCH v2 03/18] brcmsmac: remove ai_get_buscore{type,rev}() Hauke Mehrtens
2012-06-30 13:16 ` [PATCH v2 04/18] brcmsmac: use container_of instead of cast Hauke Mehrtens
2012-06-30 13:16 ` [PATCH v2 05/18] brcmsmac: remove ai_findcore() Hauke Mehrtens
2012-06-30 13:16 ` [PATCH v2 06/18] brcmsmac: remove si_pmu_init() and si_pmu_res_init() Hauke Mehrtens
2012-06-30 13:16 ` [PATCH v2 07/18] brcmsmac: remove si_pmu_spuravoid_pllupdate() Hauke Mehrtens
2012-06-30 13:16 ` [PATCH v2 08/18] brcmsmac: remove some redundant chip common workarounds Hauke Mehrtens
2012-06-30 13:16 ` [PATCH v2 09/18] brcmsmac: use core id constants from bcma Hauke Mehrtens
2012-06-30 13:16 ` [PATCH v2 10/18] brcmsmac: use chip and package " Hauke Mehrtens
2012-06-30 13:16 ` [PATCH v2 11/18] brcmsmac: remove some unnessessacry casts and void pointer Hauke Mehrtens
2012-07-01 23:59   ` Julian Calaby
2012-07-02  7:54     ` Dominique Martinet
2012-07-02 17:44       ` Hauke Mehrtens
2012-07-02 23:01         ` Julian Calaby
2012-06-30 13:16 ` [PATCH v2 12/18] brcmsmac: add a conditions for core rev 17 again Hauke Mehrtens
2012-07-03  7:06   ` Arend van Spriel
2012-06-30 13:16 ` [PATCH v2 13/18] brcmsmac: add some workarounds for other chips again Hauke Mehrtens
2012-07-03  7:08   ` Arend van Spriel
2012-06-30 13:16 ` [PATCH v2 14/18] brcmsmac: extend xmtfifo_sz array Hauke Mehrtens
2012-07-02  0:01   ` Julian Calaby
2012-07-02 18:15     ` [PATCH v3 " Hauke Mehrtens
2012-07-03  7:08   ` [PATCH v2 " Arend van Spriel
2012-06-30 13:16 ` [PATCH v2 15/18] brcmsmac: fix DMA on SoCs Hauke Mehrtens
2012-07-03  7:10   ` Arend van Spriel
2012-06-30 13:16 ` [PATCH v2 16/18] brcmsmac: extend brcms_c_chipmatch() to also handle non PCIe devices Hauke Mehrtens
2012-07-03  7:11   ` Arend van Spriel
2012-06-30 13:16 ` [PATCH v2 17/18] brcmsmac: fix read in write_phy_reg Hauke Mehrtens
2012-06-30 13:16 ` [PATCH v2 18/18] brcmsmac: handle non PCI devices in the phy code Hauke Mehrtens
2012-07-03  7:11   ` Arend van Spriel
2012-07-02  0:04 ` [PATCH v2 00/18] brcmsmac: update to get SoCs working Julian Calaby
2012-07-03  7:13 ` Arend van Spriel
2012-07-06 18:35   ` John W. Linville
2012-07-08 19:10     ` Arend van Spriel [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=4FF9DB2F.3080606@broadcom.com \
    --to=arend@broadcom.com \
    --cc=brcm80211-dev-list@broadcom.com \
    --cc=hauke@hauke-m.de \
    --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 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).