linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Hauke Mehrtens" <hauke@hauke-m.de>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 00/19] brcmsmac: use sprom and PCIe code from bcma
Date: Tue, 1 May 2012 11:35:04 +0200	[thread overview]
Message-ID: <4F9FAE48.10102@broadcom.com> (raw)
In-Reply-To: <4F9DC495.7060103@hauke-m.de>

On 04/30/2012 12:45 AM, Hauke Mehrtens wrote:
> On 04/29/2012 06:45 PM, Arend van Spriel wrote:
>> 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
>

Yes, the firmware for brcmsmac is specifically for 43224, 43225, and 
4313. I have to check with the firmware guys here what is needed for 4718.

Gr. AvS


  reply	other threads:[~2012-05-01  9:35 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
2012-05-01  9:35         ` Arend van Spriel [this message]
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=4F9FAE48.10102@broadcom.com \
    --to=arend@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).