All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Wahren <stefan.wahren@i2se.com>
To: Arend van Spriel <arend.vanspriel@broadcom.com>,
	Chi-Hsien Lin <chi-hsien.lin@cypress.com>,
	Franky Lin <franky.lin@broadcom.com>,
	Hante Meuleman <hante.meuleman@broadcom.com>,
	Wright Feng <wright.feng@cypress.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	Kevin Hilman <khilman@baylibre.com>
Subject: Re: brcmfmac: Updating Broadcom/Cypress Wifi/BT firmware
Date: Mon, 14 May 2018 11:52:56 +0200	[thread overview]
Message-ID: <944ad773-6a7a-17c5-1d7e-0a3d20173e1d@i2se.com> (raw)
In-Reply-To: <5AF945B8.3070801@broadcom.com>

Hi Arend,

Am 14.05.2018 um 10:15 schrieb Arend van Spriel:
> On 5/2/2018 8:05 PM, Stefan Wahren wrote:
>> Hi,
>> i wanted to know, if there are any plans to update the 
>> Broadcom/Cypress firmware under:
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git 
>>
>>
>> As BCM2835 maintainer i'm interested in the following files:
>>
>> brcm/brcmfmac43430-sdio.bin
>> brcm/brcmfmac43455-sdio.bin
>
> To my knowledge (just checked ;-) ) these are already in the repository.

i know, but the subject was about updating. These files are from 
2015/2016 and contains a lot of issues (including CVE-2016-0801 
CVE-2017-0561 CVE-2017-9417).

AFAIK the latest version of brcmfmac43430-sdio.bin was from October 2017 
[1].

>
>> brcm/brcmfmac43430-sdio.txt
>
> We do not distribute these .txt files aka nvram files as they are 
> board specific and no good solution to express that in the filename.

Thanks for clarification

>
>> brcm/BCM43430A1.hcd
>
> The BT side is not handled by us. Might be different within Cypress 
> though.

Okay

>
> Regards,
> Arend

[1] - https://github.com/raspberrypi/linux/issues/1342

Best regards
Stefan

  reply	other threads:[~2018-05-14  9:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-02 18:05 brcmfmac: Updating Broadcom/Cypress Wifi/BT firmware Stefan Wahren
2018-05-14  8:15 ` Arend van Spriel
2018-05-14  9:52   ` Stefan Wahren [this message]
2018-05-14 11:56     ` James Hughes

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=944ad773-6a7a-17c5-1d7e-0a3d20173e1d@i2se.com \
    --to=stefan.wahren@i2se.com \
    --cc=arend.vanspriel@broadcom.com \
    --cc=chi-hsien.lin@cypress.com \
    --cc=franky.lin@broadcom.com \
    --cc=hante.meuleman@broadcom.com \
    --cc=khilman@baylibre.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=wright.feng@cypress.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.