From: Chi-Hsien Lin <Chi-Hsien.Lin@cypress.com>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: "franky.lin@broadcom.com" <franky.lin@broadcom.com>,
"hante.meuleman@broadcom.com" <hante.meuleman@broadcom.com>,
Wright Feng <Wright.Feng@cypress.com>,
"brcm80211-dev-list.pdl@broadcom.com"
<brcm80211-dev-list.pdl@broadcom.com>,
brcm80211-dev-list <brcm80211-dev-list@cypress.com>
Subject: Re: BCM4335 SDIO firmware crash/problem
Date: Tue, 19 Nov 2019 14:35:22 +0000 [thread overview]
Message-ID: <f8351761-b5b4-734d-7fc8-aae37023d222@cypress.com> (raw)
In-Reply-To: <8c5c682c-da4b-0fb4-2173-8c3082614a56@broadcom.com>
On 11/19/2019 4:53, Arend Van Spriel wrote:
> On 11/18/2019 9:47 PM, Martin Blumenstingl wrote:
>> Hi Arend and linux-wireless supporters,
>>
>> On Sat, Nov 9, 2019 at 3:55 PM Martin Blumenstingl
>> <martin.blumenstingl@googlemail.com> wrote:
>>>
>>> On Sun, Nov 3, 2019 at 12:49 PM Martin Blumenstingl
>>> <martin.blumenstingl@googlemail.com> wrote:
>>> [...]
>>>> The Android installation that my device came with ships a newer
>>>> firmware version: "BCM4335/1 wl0: May 18 2014 16:56:54 version
>>>> 6.34.171.58.2". This is also available in CoreELEC's repository: [2].
>>>> I went ahead and used this newer on my Arch Linux ARM installation and
>>>> it seems to have fixed my problem
>>> I am now at 12 days of uptime and wifi is still working with that
>>> firmware
>> gentle ping on this
>> I can send a patch against linux-firmware if you want but I'm not sure
>> about the license or any internals of that firmware
>
> Hi Martin,
>
> Sorry I did not chime in earlier. I have not looked at the CoreELEC
> repository for license files. Without such info I am inclined to say you
> are not licensed to redistribute the firmware. The BCM4335 is
> end-of-life for us although maybe Cypress is still selling the device
> and may want to provide a firmware update.
Hi Martin/Arend,
4335 is not in our supported chip list, either.
I did a quick search and found below CoreELEC repo, but don't see a
license with it:
https://github.com/CoreELEC/brcmfmac_sdio-firmware-aml
Regards,
Chi-hsien Lin
>
> Regards,
> Arend
> .
>
next prev parent reply other threads:[~2019-11-19 14:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-03 11:49 BCM4335 SDIO firmware crash/problem Martin Blumenstingl
2019-11-09 14:55 ` Martin Blumenstingl
2019-11-18 20:47 ` Martin Blumenstingl
2019-11-19 8:53 ` Arend Van Spriel
2019-11-19 14:35 ` Chi-Hsien Lin [this message]
2019-11-20 18:32 ` Martin Blumenstingl
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=f8351761-b5b4-734d-7fc8-aae37023d222@cypress.com \
--to=chi-hsien.lin@cypress.com \
--cc=Wright.Feng@cypress.com \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211-dev-list@cypress.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.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).