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
Message-ID: <1748296.zsF0Cc0pRr@bentobox> (sfid-20170315_090423_874507_D802F5C1)
In-Reply-To: <3853747.Q0JJmSnsYM@debian64>
References: <20170310080615.22958-1-sven.eckelmann@openmesh.com> <20170310080615.22958-2-sven.eckelmann@openmesh.com> <3853747.Q0JJmSnsYM@debian64>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart106399533.3sBb3xub9B"; micalg="pgp-sha512"; protocol="application/pgp-signature"
Sender: linux-wireless-owner@vger.kernel.org

--nextPart106399533.3sBb3xub9B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"

On Freitag, 10. M=E4rz 2017 19:20:54 CET Christian Lamparter wrote:
[...]
> @Aeolus Yang / Kalle / QCA: Would it be possible to assign a variant stri=
ng to
> the Asus RT-AC58U?
>=20
> I've attached the necessary bmi-board-id=3D16 and bmi-board-id=3D17 board=
=20
> 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=20
integrated in the official [1] QCA40XX board-2.bin? OpenMesh received a boa=
rd=20
which required modified BDFs for bmi-board-id=3D16 and bmi-board-id=3D17. T=
his BDF=20
was generated by QCA and the ODM and of course conflicts with the
bmi-board-id=3D16/17 file in the official QCA40XX board-2.bin. The variant=
=20
string method [2,3] is currently the only way to have all these conflicting=
=20
files in the same board-2.bin.

Having the RT-AC58U already integrated in the official board-2.bin would be=
=20
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.=20

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-firmwa=
re.git/
[2] https://patchwork.kernel.org/patch/9615179/
[3] https://patchwork.kernel.org/patch/9615181/
--nextPart106399533.3sBb3xub9B
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEF10rh2Elc9zjMuACXYcKB8Eme0YFAljI9XoACgkQXYcKB8Em
e0b+8g/9G3GoaQ5bdQ2WdPNXZBoxdL9yW4Pql8WLep5maTbm9p6zMmngdZ6tGgEG
8DfiPqXabi4RdKh/xt+3m8DrA9p4reaeIQJqeMSD5oQUEn60oYMdkAszH/RelVfd
VCmi6Qyv0xDp25C/zCaqWe3BVfaRqf6oD9cZJy8dAfB5IQGqXXVaSQCEjQqhhh4D
8J54aDKjyx0eTbjzj/N1hRoOMEsUZAcInrG7uiCgQnO6MsF3+hkSVFIHY+hQ72Dp
OYx0sfCS9xr2NpeHgWGAuTCO2fcZgEyiyy3zryN3uBP4sT9bWYfIxtzBXD/MmPFP
JlkK2RmWwWxvexhE7R+yyQZUHkrnam7s8JqUoqtStl9ZwwztVWchGpjxq6ud3lh7
oRcICVt4VbasiStrNsiqHw+jj8/Ar+Oy4qPfJeNqCy7r8boHS4sG2ehi+uhTgb6T
wsz6VC6uNn5kWoijVulMCNqy5B5sDBHkM5KQ5jqRtLxmImF3WyViv3+njLJwEysx
F+OjbhM+NRXmtduJQ2JyrSn0BUu6IcIX+qzFCxVL7YAP/gDHEW/2jCWBh1WAxNe2
p0ryCBF8ebBXEgCiLLrBUN00xSf7+zDJ3+hFoTx9AzA0L5yFqfzGD5Aanmq+8k7g
Rkkgac8kXYAy/BcIs7DWxhEfB/giH/VK3km2KSbJV63oVjgoEkc=
=yKB9
-----END PGP SIGNATURE-----

--nextPart106399533.3sBb3xub9B--