Linux wireless drivers development
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: <linux-firmware@kernel.org>
Cc: <linux-wireless@vger.kernel.org>, <ath10k@lists.infradead.org>
Subject: [PATCH 2/3] ath10k: QCA6174 hw3.0: update board-2.bin
Date: Mon, 18 Sep 2017 18:00:56 +0300	[thread overview]
Message-ID: <1505746857-31938-3-git-send-email-kvalo@qca.qualcomm.com> (raw)
In-Reply-To: <1505746857-31938-1-git-send-email-kvalo@qca.qualcomm.com>

Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
---
 ath10k/QCA6174/hw3.0/board-2.bin | Bin 477060 -> 501748 bytes
 1 file changed, 0 insertions(+), 0 deletions(-)

diff --git a/ath10k/QCA6174/hw3.0/board-2.bin b/ath10k/QCA6174/hw3.0/board-2.bin
index a442315503bfc70f5a5fbfaa6f04004702d8474c..10960ba28975ed1c7c4e9fb91b4742f1c2ecba33 100644
GIT binary patch
delta 587
zcmZqam;G{HuAzmog{g(Pg{6hHg>4Iai~D2)NtWprs;t3^#%3moI%SDPnTdHNwl1#m
z2Bt<vxr_`941453_~YWucM`NX>KCmkD23pvmdT4iYzVz(N5LWp2J?Yzi1>1#dI+wn
z2dQ7a21F|)B#6o<gfoF~ctR)(j8=$O5RDIqVDb1+aS$6si-n1af-ygs5h?}|2o>9`
zD9OUOeTF~lTi*H|d(ZlX#ijL4+kf0AX3LJf2aleG(J=9#q)Cf59cExa7x#(jnQ#{9
zR~QXc-?#rb0|P=mL>?v{6&DvL6DJo3qGROb;v%Ht<m%(%B;|r7BIDvB7#P3`pb{YQ
zD4=o>fYA{k1we6O2}wCQ36Oe-JWM<)E-Fe2=%A=r2n`gEm6T;*0GSU~k0uUOx}9wj
zlOWUfD|;BjSy@btO_MhFE3hj}H+#w=DhP^Pq{vL02#!oK?2$QHCeuhPNmM==7(Xe%
Q_(=lB50u`Vl4&3g0Lc2w3IG5A

delta 23
ecmexzUaqBIwxNZwg{g(Pg{6hHg>4Iai#q^tr3gg;

-- 
2.7.4

  parent reply	other threads:[~2017-09-18 15:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-18 15:00 [PATCH 0/3] linux-firmware: ath10k update 20170918 Kalle Valo
2017-09-18 15:00 ` [PATCH 1/3] ath10k: QCA6174 hw3.0: update firmware-6.bin to WLAN.RM.4.4.1-00051-QCARMSWP-1 Kalle Valo
2017-09-18 15:00 ` Kalle Valo [this message]
2017-09-18 15:00 ` [PATCH 3/3] Revert "ath10k: QCA988X hw2.0: update firmware to 10.2.4.70.63-2" Kalle Valo
2017-09-18 15:14   ` Matteo Croce
2017-10-04  8:44 ` [PATCH 0/3] linux-firmware: ath10k update 20170918 Kalle Valo
2017-10-09 16:46 ` Ben Hutchings

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=1505746857-31938-3-git-send-email-kvalo@qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --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