From: Kalle Valo <kvalo@qca.qualcomm.com>
To: ben@decadent.org.uk
Cc: dwmw2@infradead.org, linux-wireless@vger.kernel.org,
ath10k@lists.infradead.org
Subject: Re: [PATCH 3/3] ath10k: add firmware files
Date: Fri, 14 Mar 2014 11:03:01 +0200 [thread overview]
Message-ID: <87wqfx8856.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20140314084514.23100.72654.stgit@x230> (Kalle Valo's message of "Fri, 14 Mar 2014 10:45:14 +0200")
Kalle Valo <kvalo@qca.qualcomm.com> writes:
> Add firmware files for ath10k wireless driver with the new QCA license.
>
> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
> ---
> LICENCE.qca | 44 +++++++++++++++++++++++++++++++++++
> WHENCE | 9 +++++++
> ath10k/QCA988X/hw2.0/board.bin | Bin
> ath10k/QCA988X/hw2.0/firmware-2.bin | Bin
> 4 files changed, 53 insertions(+)
I forgot to mention in the commit log that the version of this firmware
is 10.1.467.2-1.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: <ben@decadent.org.uk>
Cc: <linux-wireless@vger.kernel.org>, <dwmw2@infradead.org>,
<ath10k@lists.infradead.org>
Subject: Re: [PATCH 3/3] ath10k: add firmware files
Date: Fri, 14 Mar 2014 11:03:01 +0200 [thread overview]
Message-ID: <87wqfx8856.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20140314084514.23100.72654.stgit@x230> (Kalle Valo's message of "Fri, 14 Mar 2014 10:45:14 +0200")
Kalle Valo <kvalo@qca.qualcomm.com> writes:
> Add firmware files for ath10k wireless driver with the new QCA license.
>
> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
> ---
> LICENCE.qca | 44 +++++++++++++++++++++++++++++++++++
> WHENCE | 9 +++++++
> ath10k/QCA988X/hw2.0/board.bin | Bin
> ath10k/QCA988X/hw2.0/firmware-2.bin | Bin
> 4 files changed, 53 insertions(+)
I forgot to mention in the commit log that the version of this firmware
is 10.1.467.2-1.
--
Kalle Valo
next prev parent reply other threads:[~2014-03-14 9:03 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 8:45 [PATCH 1/3] Rename LICENSE.atheros_firmware to LICENCE.old_qca Kalle Valo
2014-03-14 8:45 ` Kalle Valo
2014-03-14 8:45 ` [PATCH 2/3] ath6k: remove AR6003.1 firmware Kalle Valo
2014-03-14 8:45 ` Kalle Valo
2014-03-16 18:24 ` Ben Hutchings
2014-03-16 18:24 ` Ben Hutchings
2014-03-14 8:45 ` [PATCH 3/3] ath10k: add firmware files Kalle Valo
2014-03-14 8:45 ` Kalle Valo
2014-03-14 9:03 ` Kalle Valo [this message]
2014-03-14 9:03 ` Kalle Valo
2014-03-16 18:25 ` Ben Hutchings
2014-03-16 18:25 ` Ben Hutchings
2014-03-14 12:36 ` Luis R. Rodriguez
2014-03-14 12:36 ` Luis R. Rodriguez
2014-03-14 12:47 ` Dave Taht
2014-03-14 12:47 ` Dave Taht
2014-03-14 15:23 ` Arend van Spriel
2014-03-14 15:23 ` Arend van Spriel
2014-03-14 17:07 ` Kalle Valo
2014-03-14 17:07 ` Kalle Valo
2014-03-14 17:25 ` Luis R. Rodriguez
2014-03-14 17:25 ` Luis R. Rodriguez
2014-03-16 18:57 ` Ben Hutchings
2014-03-16 18:57 ` Ben Hutchings
2014-03-16 20:17 ` Luis R. Rodriguez
2014-03-16 20:17 ` Luis R. Rodriguez
2014-06-25 15:47 ` Luis R. Rodriguez
2014-06-25 15:47 ` Luis R. Rodriguez
2014-03-17 8:45 ` Alex Hacker
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=87wqfx8856.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=ben@decadent.org.uk \
--cc=dwmw2@infradead.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 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.