From: Sven Eckelmann <sven.eckelmann@openmesh.com>
To: Aeolus Yang <aeolus@qti.qualcomm.com>
Cc: Adrian Chadd <adrian@freebsd.org>,
linux-wireless@vger.kernel.org, ath10k@lists.infradead.org,
Raja Mani <rmani@codeaurora.org>,
simon.wunderlich@openmesh.com, john@phrozen.org,
Christian Lamparter <chunkeey@googlemail.com>,
ext.waldemar.rymarkiewicz@tieto.com, kvalo@codeaurora.org
Subject: Re: [PATCH 2/2] ath10k: search DT for qcom, ath10k-calibration-variant
Date: Wed, 15 Mar 2017 09:04:10 +0100 [thread overview]
Message-ID: <1748296.zsF0Cc0pRr@bentobox> (raw)
In-Reply-To: <3853747.Q0JJmSnsYM@debian64>
[-- Attachment #1.1: Type: text/plain, Size: 1536 bytes --]
On Freitag, 10. März 2017 19:20:54 CET Christian Lamparter wrote:
[...]
> @Aeolus Yang / Kalle / QCA: Would it be possible to assign a variant string to
> the Asus RT-AC58U?
>
> I've attached the necessary bmi-board-id=16 and bmi-board-id=17 board
> files to this mail as well. So, all that needs to be done is to add
> them to the board-2.bin on your codeaurora / ath10k-firmware project.
@Aeolus Yang / QCA, any new infos how these BDFs or similar ones can be
integrated in the official [1] QCA40XX board-2.bin? OpenMesh received a board
which required modified BDFs for bmi-board-id=16 and bmi-board-id=17. This BDF
was generated by QCA and the ODM and of course conflicts with the
bmi-board-id=16/17 file in the official QCA40XX board-2.bin. The variant
string method [2,3] is currently the only way to have all these conflicting
files in the same board-2.bin.
Having the RT-AC58U already integrated in the official board-2.bin would be
good example and would reduce the barrier for other vendors (with the same
problem) a lot. For example OpenMesh could then use the same approach to get
their BDFs integrated.
Kind regards,
Sven
[1] "official" as in "part of the official repositories"
* https://github.com/kvalo/ath10k-firmware
* https://source.codeaurora.org/quic/qsdk/oss/firmware/ath10k-firmware
* https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/
[2] https://patchwork.kernel.org/patch/9615179/
[3] https://patchwork.kernel.org/patch/9615181/
[-- 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
WARNING: multiple messages have this Message-ID (diff)
From: Sven Eckelmann <sven.eckelmann@openmesh.com>
To: Aeolus Yang <aeolus@qti.qualcomm.com>
Cc: Christian Lamparter <chunkeey@googlemail.com>,
ext.waldemar.rymarkiewicz@tieto.com, ath10k@lists.infradead.org,
linux-wireless@vger.kernel.org, kvalo@codeaurora.org,
Adrian Chadd <adrian@freebsd.org>,
john@phrozen.org, Raja Mani <rmani@codeaurora.org>,
simon.wunderlich@openmesh.com
Subject: Re: [PATCH 2/2] ath10k: search DT for qcom,ath10k-calibration-variant
Date: Wed, 15 Mar 2017 09:04:10 +0100 [thread overview]
Message-ID: <1748296.zsF0Cc0pRr@bentobox> (raw)
In-Reply-To: <3853747.Q0JJmSnsYM@debian64>
[-- Attachment #1: Type: text/plain, Size: 1536 bytes --]
On Freitag, 10. März 2017 19:20:54 CET Christian Lamparter wrote:
[...]
> @Aeolus Yang / Kalle / QCA: Would it be possible to assign a variant string to
> the Asus RT-AC58U?
>
> I've attached the necessary bmi-board-id=16 and bmi-board-id=17 board
> files to this mail as well. So, all that needs to be done is to add
> them to the board-2.bin on your codeaurora / ath10k-firmware project.
@Aeolus Yang / QCA, any new infos how these BDFs or similar ones can be
integrated in the official [1] QCA40XX board-2.bin? OpenMesh received a board
which required modified BDFs for bmi-board-id=16 and bmi-board-id=17. This BDF
was generated by QCA and the ODM and of course conflicts with the
bmi-board-id=16/17 file in the official QCA40XX board-2.bin. The variant
string method [2,3] is currently the only way to have all these conflicting
files in the same board-2.bin.
Having the RT-AC58U already integrated in the official board-2.bin would be
good example and would reduce the barrier for other vendors (with the same
problem) a lot. For example OpenMesh could then use the same approach to get
their BDFs integrated.
Kind regards,
Sven
[1] "official" as in "part of the official repositories"
* https://github.com/kvalo/ath10k-firmware
* https://source.codeaurora.org/quic/qsdk/oss/firmware/ath10k-firmware
* https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/
[2] https://patchwork.kernel.org/patch/9615179/
[3] https://patchwork.kernel.org/patch/9615181/
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-03-15 8:04 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 8:06 [PATCH 1/2] dt: bindings: add new dt entry for ath10k calibration variant Sven Eckelmann
2017-03-10 8:06 ` Sven Eckelmann
2017-03-10 8:06 ` Sven Eckelmann
2017-03-10 8:06 ` [PATCH 2/2] ath10k: search DT for qcom,ath10k-calibration-variant Sven Eckelmann
2017-03-10 8:06 ` Sven Eckelmann
2017-03-10 8:06 ` Sven Eckelmann
2017-03-10 18:20 ` [PATCH 2/2] ath10k: search DT for qcom, ath10k-calibration-variant Christian Lamparter
2017-03-10 18:20 ` [PATCH 2/2] ath10k: search DT for qcom,ath10k-calibration-variant Christian Lamparter
2017-03-15 8:04 ` Sven Eckelmann [this message]
2017-03-15 8:04 ` Sven Eckelmann
2017-08-21 7:11 ` [PATCH 2/2] ath10k: search DT for qcom, ath10k-calibration-variant Sven Eckelmann
2017-08-21 7:11 ` [PATCH 2/2] ath10k: search DT for qcom,ath10k-calibration-variant Sven Eckelmann
2017-10-27 9:34 ` [PATCH 2/2] ath10k: search DT for qcom, ath10k-calibration-variant Kalle Valo
2017-10-27 9:34 ` Kalle Valo
2017-12-08 9:50 ` Kalle Valo
2017-12-08 9:50 ` Kalle Valo
2018-01-29 20:09 ` Asus RT-AC58U boardfile (was Re: [PATCH 2/2] ath10k: search DT for qcom, ath10k-calibration-variant) Christian Lamparter
2018-01-29 20:09 ` Christian Lamparter
2018-10-08 8:21 ` Kalle Valo
2018-10-08 8:21 ` Kalle Valo
2018-04-19 14:56 ` [PATCH 2/2] ath10k: search DT for qcom, ath10k-calibration-variant Kalle Valo
2018-04-19 14:56 ` Kalle Valo
2018-04-20 19:50 ` Christian Lamparter
2018-04-20 19:50 ` Christian Lamparter
2017-12-08 9:27 ` Kalle Valo
2017-12-08 9:27 ` [PATCH 2/2] ath10k: search DT for qcom,ath10k-calibration-variant Kalle Valo
2017-12-08 9:27 ` Kalle Valo
2017-03-20 15:07 ` [PATCH 1/2] dt: bindings: add new dt entry for ath10k calibration variant Rob Herring
2017-03-20 15:07 ` Rob Herring
2017-03-20 15:07 ` Rob Herring
2017-03-20 16:28 ` Sven Eckelmann
2017-03-20 16:28 ` Sven Eckelmann
2017-03-20 16:28 ` Sven Eckelmann
2017-03-20 16:42 ` Adrian Chadd
2017-03-20 16:42 ` Adrian Chadd
2017-03-21 7:29 ` Sven Eckelmann
2017-03-21 7:29 ` Sven Eckelmann
2017-03-21 13:00 ` Rob Herring
2017-03-21 13:00 ` Rob Herring
2017-03-21 13:00 ` Rob Herring
2017-03-21 14:33 ` Sven Eckelmann
2017-03-21 14:33 ` Sven Eckelmann
2017-03-21 14:33 ` Sven Eckelmann
2017-03-22 2:56 ` Rob Herring
2017-03-22 2:56 ` Rob Herring
2017-03-22 7:20 ` Sven Eckelmann
2017-03-22 7:20 ` Sven Eckelmann
2017-12-08 9:22 ` Kalle Valo
2017-12-08 9:22 ` Kalle Valo
2017-12-08 9:22 ` 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=1748296.zsF0Cc0pRr@bentobox \
--to=sven.eckelmann@openmesh.com \
--cc=adrian@freebsd.org \
--cc=aeolus@qti.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=chunkeey@googlemail.com \
--cc=ext.waldemar.rymarkiewicz@tieto.com \
--cc=john@phrozen.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rmani@codeaurora.org \
--cc=simon.wunderlich@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 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.