From: Kalle Valo <kvalo@codeaurora.org>
To: Ben Greear <greearb@candelatech.com>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: Please add new board files for WLE1216V5-20 and another Compex NIC.
Date: Thu, 19 Apr 2018 13:10:53 +0300 [thread overview]
Message-ID: <878t9jmrpu.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <87fu3rms5k.fsf@kamboji.qca.qualcomm.com> (Kalle Valo's message of "Thu, 19 Apr 2018 10:01:29 +0000")
Kalle Valo <kvalo@qca.qualcomm.com> writes:
> Ben Greear <greearb@candelatech.com> writes:
>
>> It seems the upstream board-2.bin file for 9984 does not yet include
>> support for WLE1216V5-20
>> (or possibly it does and OpenWRT grabs the wrong one?).
>>
>> I'm attaching the board file for this NIC and for another one which
>> I have not yet tested. I received these from Compex and have
>> tested the bus=pci,bmi-chip-id=0,bmi-board-id=31-compex.bin file on the WLE1216V5-20
>>
>> Please add these into the official board-2.bin for 9984.
>
> Added, but please check carefully that I didn't do any mistakes.
>
> https://github.com/kvalo/ath10k-firmware/commit/66be3a48d9cf17ace8413cf478a5954483393af4
That's obviously the wrong commit, this is the correct one:
https://github.com/kvalo/ath10k-firmware/commit/b1dd338046a385743c483a47e8eef276adaba0c0
--
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:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 21:59 Please add new board files for WLE1216V5-20 and another Compex NIC Ben Greear
2018-04-11 15:18 ` Tim Harvey
2018-04-12 7:27 ` Sven Eckelmann
2018-04-12 16:31 ` Ben Greear
2018-04-13 10:53 ` Kalle Valo
2018-04-18 16:42 ` Kalle Valo
2018-04-18 16:52 ` Ben Greear
2018-04-19 10:01 ` Kalle Valo
2018-04-19 10:10 ` Kalle Valo [this message]
2018-04-19 17:33 ` Ben Greear
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=878t9jmrpu.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.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