From: Ben Greear <greearb@candelatech.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: Interest in getting ath10k-ct firmware support upstream?
Date: Fri, 13 Apr 2018 08:32:05 -0700 [thread overview]
Message-ID: <f902dc36-4014-4996-1522-0f1333a2473f@candelatech.com> (raw)
In-Reply-To: <87po33qlgh.fsf@kamboji.qca.qualcomm.com>
On 04/13/2018 06:34 AM, Kalle Valo wrote:
> Ben Greear <greearb@candelatech.com> writes:
>
>> I'm in the midst of porting my out-of-tree ath10k patches forward to
>> the 4.16 kernel.
>>
>> In case you are interested in allowing support for ath10k-ct firmware
>> in the upstream kernel, now would be a good time for me to work on
>> this.
>>
>> Please let me know if you are interested.
>
> I don't really know what is needed for your firmware so difficult to
> really comment. And ath10k really does not support any specific firmware
> branch per se, it uses more finegrained feature based detection anyway.
>
> But as we are adding SDIO, USB and SNOC busses to ath10k, which is quite
> a enourmous task itself, and trying to support even a different firmware
> sounds really difficult.
I have lots of mostly small tweaks, enabled by feature flags specific to my
firmware. Adding my changes will increase the code size a bit, but I don't think
it will add much fundamental complexity.
If you will accept feature flags upstream for my firmware and will make an
effort to review patches in a timely manner, I will work on a patch series
and send it for review.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2018-04-13 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 21:46 Interest in getting ath10k-ct firmware support upstream? Ben Greear
2018-04-13 13:34 ` Kalle Valo
2018-04-13 15:32 ` Ben Greear [this message]
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=f902dc36-4014-4996-1522-0f1333a2473f@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@codeaurora.org \
/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