From: Arend van Spriel <arend@broadcom.com>
To: Kyle McMartin <kyle@infradead.org>
Cc: <linux-wireless@vger.kernel.org>, Rafal Milecki <zajec5@gmail.com>
Subject: Re: [PATCH] brcmfmac: firmware refresh for BCM43602 PCIE devices
Date: Wed, 7 Oct 2015 21:57:16 +0200 [thread overview]
Message-ID: <5615791C.4060709@broadcom.com> (raw)
In-Reply-To: <20151007174855.GI26918@merlin.infradead.org>
On 10/07/2015 07:48 PM, Kyle McMartin wrote:
> On Wed, Sep 30, 2015 at 06:53:47PM +0200, Arend van Spriel wrote:
>> On 09/25/2015 02:00 AM, Kyle McMartin wrote:
>>> 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?
>>
>> Hi Kyle,
>>
>> For brcmfmac firmware we do not have version numbers in the WHENCE file. The
>> firmware file itself contains the version number which can be shown using
>> hexdump. I can make a note of that fact in the WHENCE file if needed.
>>
>
> Sorry, I meant to apply this a few days ago, but I finally pushed it
> out. Thanks for your patience.
No problem.
Thanks,
Arend
> regards, --Kyle
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2015-10-07 19:57 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
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 [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=5615791C.4060709@broadcom.com \
--to=arend@broadcom.com \
--cc=kyle@infradead.org \
--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 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).