Linux wireless drivers development
 help / color / mirror / Atom feed
From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Chi-Hsien Lin <chi-hsien.lin@cypress.com>, linux-firmware@kernel.org
Cc: linux-wireless@vger.kernel.org,
	brcm80211-dev-list <brcm80211-dev-list@cypress.com>,
	brcm80211-dev-list.pdl@broadcom.com
Subject: Re: [PATCH V2] brcm: add CYW4373 firmwares and Cypress license file
Date: Fri, 1 Dec 2017 20:57:09 +0100	[thread overview]
Message-ID: <f96ddf93-0e1d-d6f1-570b-fd3c8ec711e0@broadcom.com> (raw)
In-Reply-To: <20171201084243.GA58942@aremote07.aus.cypress.com>

On 01-12-17 09:43, Chi-Hsien Lin wrote:
> Add the CYW4373 SDIO and USB firmware files, along with the corresponding
> Cypress license file.

Just wanted to be sure. These firmware files contain a CLM to get the 
device operational, ie. no separate CLM download is needed.

Regards,
Arend

> Signed-off-by: Chi-hsien Lin<chi-hsien.lin@cypress.com>
> ---
>   LICENCE.cypress            | 139 +++++++++++++++++++++++++++++++++++++++++++++
>   WHENCE                     |   5 ++
>   brcm/brcmfmac4373-sdio.bin | Bin 0 -> 457994 bytes
>   brcm/brcmfmac4373.bin      | Bin 0 -> 479232 bytes
>   4 files changed, 144 insertions(+)
>   create mode 100644 LICENCE.cypress
>   create mode 100644 brcm/brcmfmac4373-sdio.bin
>   create mode 100644 brcm/brcmfmac4373.bin

  reply	other threads:[~2017-12-01 19:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-01  8:43 [PATCH V2] brcm: add CYW4373 firmwares and Cypress license file Chi-Hsien Lin
2017-12-01 19:57 ` Arend van Spriel [this message]
2017-12-04  3:56   ` Chi-Hsien Lin
2017-12-07  1:36 ` Kyle McMartin

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=f96ddf93-0e1d-d6f1-570b-fd3c8ec711e0@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=brcm80211-dev-list.pdl@broadcom.com \
    --cc=brcm80211-dev-list@cypress.com \
    --cc=chi-hsien.lin@cypress.com \
    --cc=linux-firmware@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    /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