From: Ben Greear <greearb@candelatech.com>
To: "Valo, Kalle" <kvalo@qca.qualcomm.com>,
Rajkumar Manoharan <rmanohar@codeaurora.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Manoharan, Rajkumar" <rmanohar@qti.qualcomm.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PATCH 2/2] ath10k: remove 10.1 firmware support
Date: Fri, 3 Jun 2016 09:20:20 -0700 [thread overview]
Message-ID: <5751AE44.8050607@candelatech.com> (raw)
In-Reply-To: <87shwuuuct.fsf@kamboji.qca.qualcomm.com>
On 06/03/2016 09:09 AM, Valo, Kalle wrote:
> Rajkumar Manoharan <rmanohar@codeaurora.org> writes:
>
>> On 2016-06-03 21:18, Ben Greear wrote:
>>> On 06/03/2016 08:33 AM, Rajkumar Manoharan wrote:
>>>> Earlier qca9888 device was brought up using 10.1 firmware and then
>>>> later all firmware fixes and new features are migrated to 10.2/10.2.x
>>>> firmware branch. As all of 10.1 funtionalities are supported in 10.2
>>>> based firmware, removing 10.1 firmware support for qca9888 device.
>>>
>>> Oh please do not do this. My 10.1 firmware works very nicely,
>>> and out-performs 10.2 in my testing. Lots of people use my firmware
>>> when they need IBSS support or other features not found in
>>> official firmware, so it is not just me that will have
>>> problems if you remove this support.
>>>
>> Aah.. I thought CT firmware is 10.2 based. Since most of firmware bug
>> fixes and enhancements are integrated into 10.2 based firmware, we
>> thought of get rid of 10.1 firmware to reduce code size. Moreover
>> existing 10.1 official firmware has known issues.
>
> Yeah, we really want to reduce the amount firmware branches to support
> in ath10k.
>
>> Is it possible to upgrade CT firmware to 10.2 WMI/HTT interfaces?
>
> That's a good idea. That shouldn't be too hard, right? I don't think HTT needs
> any changes, but for WMI few commands and ids need to be changed.
I was thinking the 10.2 mgt-over-htt API would be trouble-some to make work on
10.1 firmware. I have my own way to do mgt-over-htt in 10.1, but API
is different and I would need a small driver patch upstream
to make that work. I'm not sure what other changes would be needed, but
if it is just conditionally compiling some WMI defines, that should be
doable.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2016-06-03 16:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 15:33 [PATCH 1/2] ath10k: handle testmode events for 10.2 based firmware Rajkumar Manoharan
2016-06-03 15:33 ` [PATCH 2/2] ath10k: remove 10.1 firmware support Rajkumar Manoharan
2016-06-03 15:48 ` Ben Greear
2016-06-03 15:55 ` Rajkumar Manoharan
2016-06-03 16:07 ` Ben Greear
2016-06-03 16:28 ` Rajkumar Manoharan
2016-06-03 16:36 ` Ben Greear
2016-06-03 16:09 ` Valo, Kalle
2016-06-03 16:20 ` Ben Greear [this message]
2016-06-03 16:33 ` Valo, Kalle
2016-06-03 16:46 ` Ben Greear
2016-09-14 12:24 ` [1/2] ath10k: handle testmode events for 10.2 based firmware 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=5751AE44.8050607@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rmanohar@codeaurora.org \
--cc=rmanohar@qti.qualcomm.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;
as well as URLs for NNTP newsgroup(s).