ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Sven Eckelmann <sven.eckelmann@openmesh.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
	Christian Lamparter <chunkeey@gmail.com>
Subject: Re: ath10k-firmware: QCA4019 hw1.0: Add OpenMesh A42 specific BDFs
Date: Fri, 26 Jan 2018 16:07:10 +0000	[thread overview]
Message-ID: <874ln8txhu.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <6906010.WJMafUttCS@bentobox> (Sven Eckelmann's message of "Tue,  28 Nov 2017 15:45:52 +0100")

Sven Eckelmann <sven.eckelmann@openmesh.com> writes:

> Hi,
>
> I am currently trying to integrate the OpenMesh A42 support in LEDE [1]. This 
> AP requires two special BDFs to get the Wi-Fi PHYs working (correctly). The 
> bmi-board-id='s would clash with one of the the IPQ401X AP-DK boards because
> QCA doesn't provide special IDs for customers and seems to use the AP-DK
> board-ids in the wifi firmware to change its behavior. But we've already
> proposed a patch to work around this kind of problem [2].
>
> The name of the files are equal to the id string in the board-2.bin (minus the 
> ".bin"):
>
> * bus=ahb,bmi-chip-id=0,bmi-board-id=16,variant=OM-A42
>   - sha256sum: 
>     10700a7ac636d57fe055e5bb4bd5f7bb3f1c282a7f25a8bb2204fc36e8c317bf
> * bus=ahb,bmi-chip-id=0,bmi-board-id=17,variant=OM-A42
>   - sha256sum:
>     b3d9556894e509ac608b2e27c9169da12c63634670bb69c5ef21fb31583e7998

I added these now:

https://github.com/kvalo/ath10k-firmware/commit/5cd2bacd8e22217335e539b416d0cb8d59f8e312

To make this easier I did some bigger changes in ath10k-bdencoder,
please check carefully that I didn't break anything.

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

  parent reply	other threads:[~2018-01-26 16:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-28 14:45 ath10k-firmware: QCA4019 hw1.0: Add OpenMesh A42 specific BDFs Sven Eckelmann
2017-12-08 10:10 ` Sven Eckelmann
2018-01-26 16:07 ` Kalle Valo [this message]
2018-01-29  7:59   ` Sven Eckelmann
2018-01-29 11:10     ` 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=874ln8txhu.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=chunkeey@gmail.com \
    --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