ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven.eckelmann@openmesh.com>
To: ath10k@lists.infradead.org
Cc: Christian Lamparter <chunkeey@googlemail.com>,
	Kalle Valo <kvalo@codeaurora.org>
Subject: Re: ath10k-firmware: QCA4019 hw1.0: Add FRITZ!Box 4040 specific BDFs
Date: Thu, 19 Apr 2018 13:50:03 +0200	[thread overview]
Message-ID: <6134582.leX8xKhRDT@bentobox> (raw)
In-Reply-To: <10659485.WSGLUWTQ6L@bentobox>


[-- Attachment #1.1: Type: text/plain, Size: 2191 bytes --]

On Dienstag, 17. April 2018 10:15:42 CEST Sven Eckelmann wrote:
[...]
>   - QCA4019 hw1.0
> 
>     + bus=ahb,bmi-chip-id=0,bmi-board-id=16,variant=AVM-FRITZBox-4040
>       sha256sum:
>       eb866d036149fe4ba35f3f9d0d97e51969b1f1dbac6ea962daf9012ffa75427a
>     + bus=ahb,bmi-chip-id=0,bmi-board-id=17,variant=AVM-FRITZBox-4040
>       sha256sum:
>       f3dc3c2f10037722006e9e7e5173a7468649e9a554f564323f9580f4a8bba10a

Thanks,

looks like the boardata files were added in
https://github.com/kvalo/ath10k-firmware/commit/81a745e6a529565438ee4aea357a8a59e9564848

pending
=======

* Asus RT-AC58U

  - submitted before the guide was published
  - http://lists.infradead.org/pipermail/ath10k/2017-March/009454.html

* Netgear EX6100v2/EX6150v2

  - http://lists.infradead.org/pipermail/ath10k/2018-February/010845.html

* 8devices Jalapeno

  - http://lists.infradead.org/pipermail/ath10k/2018-March/010916.html

* GL.iNet GL-B1300

  - http://lists.infradead.org/pipermail/ath10k/2018-March/011058.html

* OpenMesh A62

  - http://lists.infradead.org/pipermail/ath10k/2018-March/011081.html
  - QCA4019 files added in 
    https://github.com/kvalo/ath10k-firmware/commit/a262aac7cfe5ae5833378b4f1b0634f873a4df4d
  - "bus=pci,bmi-chip-id=0,bmi-board-id=16,variant=OM-A62" must still 
    be moved to QCA9888 hw 2.0 board-2.bin


accepted
========

* OpenMesh A42

  - http://lists.infradead.org/pipermail/ath10k/2017-November/010470.html
  - http://lists.infradead.org/pipermail/ath10k/2017-December/010543.html
  - https://github.com/kvalo/ath10k-firmware/commit/5cd2bacd8e22217335e539b416d0cb8d59f8e312

* Meraki MR33

  - http://lists.infradead.org/pipermail/ath10k/2018-April/011179.html
  - https://github.com/kvalo/ath10k-firmware/commit/66be3a48d9cf17ace8413cf478a5954483393af4

* Compex WLE1216V5-20 + Compex ?

  - http://lists.infradead.org/pipermail/ath10k/2018-March/010998.html
  - https://github.com/kvalo/ath10k-firmware/commit/b1dd338046a385743c483a47e8eef276adaba0c0

* AVM FRITZ!Box 4040

  - http://lists.infradead.org/pipermail/ath10k/2018-April/011178.html
  - https://github.com/kvalo/ath10k-firmware/commit/81a745e6a529565438ee4aea357a8a59e9564848

Kind regards,
	Sven

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 146 bytes --]

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  parent reply	other threads:[~2018-04-19 11:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-17  8:15 ath10k-firmware: QCA4019 hw1.0: Add FRITZ!Box 4040 specific BDFs Sven Eckelmann
2018-04-17 10:38 ` Christian Lamparter
2018-04-19 11:50 ` Sven Eckelmann [this message]
2018-04-19 11:50 ` Kalle Valo

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=6134582.leX8xKhRDT@bentobox \
    --to=sven.eckelmann@openmesh.com \
    --cc=ath10k@lists.infradead.org \
    --cc=chunkeey@googlemail.com \
    --cc=kvalo@codeaurora.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