From: Kalle Valo <kvalo@codeaurora.org>
To: Sven Eckelmann <sven.eckelmann@openmesh.com>
Cc: ath10k@lists.infradead.org
Subject: Re: ath10k-firmware: QCA4019 hw1.0/QCA9888 hw2.0: Add OpenMesh A62 specific BDFs
Date: Thu, 19 Apr 2018 13:12:19 +0300 [thread overview]
Message-ID: <874lk7mrng.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <3706510.gbe5VexPLA@bentobox> (Sven Eckelmann's message of "Thu, 29 Mar 2018 12:11:02 +0200")
Sven Eckelmann <sven.eckelmann@openmesh.com> writes:
> * ids to be used with the board file (ATH10K_BD_IE_BOARD_NAME in ath10k)
>
> - QCA4019 hw1.0
>
> + bus=ahb,bmi-chip-id=0,bmi-board-id=20,variant=OM-A62
> sha256sum:
> df5dc5a55506e2a58dcb0b8542f40226d3bfd530a6fc0bc90c728ab18a57144c
> + bus=ahb,bmi-chip-id=0,bmi-board-id=21,variant=OM-A62
> sha256sum:
> 96c3d044fe26522c75313c210ace6f85d5bdcdbce3350214d92467501a01fb88
>
> - QCA9888 hw2.0
>
> + bus=pci,bmi-chip-id=0,bmi-board-id=16,variant=OM-A62
> sha256sum:
> c85b23763e748abeb7e8c42e243dab1fc58d1bff94111e4058bdf31ddb14cefa
BTW, in the future md5sum would be more useful as ath10k-bdencoder
--info prints that. I added that to the wiki as well:
https://wireless.wiki.kernel.org/en/users/drivers/ath10k/boardfiles
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2018-04-19 10:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 10:11 ath10k-firmware: QCA4019 hw1.0/QCA9888 hw2.0: Add OpenMesh A62 specific BDFs Sven Eckelmann
2018-04-19 10:12 ` Kalle Valo [this message]
2018-04-19 10:20 ` Kalle Valo
2018-04-19 10:57 ` Sven Eckelmann
2018-04-19 14:21 ` Kalle Valo
2018-04-19 14:33 ` Kalle Valo
2018-04-19 14:47 ` Sven Eckelmann
2018-04-19 15:11 ` Kalle Valo
2018-04-20 7:05 ` Sven Eckelmann
2018-04-19 16:28 ` Christian Lamparter
2018-04-19 16:51 ` 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=874lk7mrng.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=sven.eckelmann@openmesh.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