All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kyle McMartin <kyle@infradead.org>
To: Arend van Spriel <arend@broadcom.com>
Cc: linux-wireless@vger.kernel.org, Rafal Milecki <zajec5@gmail.com>
Subject: Re: [PATCH] brcmfmac: firmware refresh for BCM43602 PCIE devices
Date: Thu, 24 Sep 2015 20:00:04 -0400	[thread overview]
Message-ID: <20150925000004.GF26918@merlin.infradead.org> (raw)
In-Reply-To: <1443120304-11153-1-git-send-email-arend@broadcom.com>

On Thu, Sep 24, 2015 at 08:45:04PM +0200, Arend van Spriel wrote:
> A number of end-users reported issues with BCM43602 on the 2015
> MacBook Pro. It turned out the previously released firmware did
> not properly support that device [1]. Hence an update of the STA
> firmware and while at it refresh the AP firmware as well. The
> latter has been tested using Netgear R8000. The STA firmware has
> been tested on MacBook Pro.
> 

Are there version numbers we could update in WHENCE to make this
easier to track?

regards, --jkkm

> [1] https://bugzilla.kernel.org/show_bug.cgi?id=100201
> 
> Cc: Rafal Milecki <zajec5@gmail.com>
> Tested-by: Knuth Posern <knuth@posern.org>
> Reviewed-by: Pieter-Paul Giesberts <pieterpg@broadcom.com>
> Signed-off-by: Arend van Spriel <arend@broadcom.com>
> ---
> This patch fixes a couple of issues mentioned in kernel bugzilla
> #100201 with 2015 MacBook Pro machines using this wifi chipset.
> 
> The patch applies to master branch of the linux-firmware repository
> on top of commit f88e5c2e2ff5 ("Merge 'c11384c' of
> git://people.freedesktop.org/~vivijim/linux-firmware...").

  reply	other threads:[~2015-09-25  0:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24 18:45 [PATCH] brcmfmac: firmware refresh for BCM43602 PCIE devices Arend van Spriel
2015-09-25  0:00 ` Kyle McMartin [this message]
2015-09-25 18:12   ` Arend van Spriel
2015-09-30 16:53   ` Arend van Spriel
2015-10-07 17:48     ` Kyle McMartin
2015-10-07 19:57       ` 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=20150925000004.GF26918@merlin.infradead.org \
    --to=kyle@infradead.org \
    --cc=arend@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=zajec5@gmail.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.