ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Sebastian Gottschall <s.gottschall@dd-wrt.com>,
	ath10k@lists.infradead.org
Subject: Re: Stand-alone ath10k-ct driver.
Date: Mon, 20 Jun 2016 16:19:33 -0700	[thread overview]
Message-ID: <57687A05.3080400@candelatech.com> (raw)
In-Reply-To: <1c702fd0-677c-82e3-ddbe-ab4335a4a1a6@dd-wrt.com>

On 06/20/2016 04:11 PM, Sebastian Gottschall wrote:
> Am 20.06.2016 um 23:52 schrieb Ben Greear:
>> Hello!
>>
>> I have made an attempt to provide a stand-alone ath10k driver that should compile
>> and work against stock 4.7 kernels.  This should provide better support for CT ath10k
>> firmware without having to apply large numbers of patches.  My 4.7 kernel has only been very lightly tested
>> to date, and the stand-alone driver is only compile tested.  I will update the
>> ath-ct repo often as testing progresses on 4.7.
>>
>> If there are brave souls that want to try it out, I'd appreciate any feedback.
>>
>> https://github.com/greearb/ath-ct
>>
>> See the README.txt for some details.  This will require at least some familiarity
>> with building kernels since I do not have any nice automation to compile against
>> the current running kernel yet, for instance.
>>
> why dont you use compat-wireless / backports as base?
> so you can use your driver in any kernel version

Just no time to deal with backports, and if I have just a stand-alone driver,
then it is easier for folks to use it in whatever kernel they already happen
to be using.  Hopefully some project that is already using a 4.7-ish backport
can compile my driver against that and have it just work, for instance.

Since I'm finding so many regressions when I rebase, and rebasing makes it almost
impossible to bisect between kernels, then maybe it would just be better if
I maintained a parallel drivers/net/wireless/ath/ath10k-ct/, and just applied
patches from ../ath10k/ manually on top of my own stuff.  At least that way
I could bisect regressions....

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

      reply	other threads:[~2016-06-20 23:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-20 21:52 Stand-alone ath10k-ct driver Ben Greear
2016-06-20 23:11 ` Sebastian Gottschall
2016-06-20 23:19   ` 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=57687A05.3080400@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    --cc=s.gottschall@dd-wrt.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