From: Ben Greear <greearb@candelatech.com>
To: "Marcel H." <maco@blava.net>, ath10k@lists.infradead.org
Subject: Re: [SPAM] Re: WLE600VX from PCEngines
Date: Wed, 09 Sep 2015 11:22:28 -0700 [thread overview]
Message-ID: <55F078E4.2050409@candelatech.com> (raw)
In-Reply-To: <CAGNwC3nyHCkmhOcYF31MCRXxoE7PsJ==rz=ohLwCNiZNokQxtw@mail.gmail.com>
On 09/09/2015 04:40 AM, Marcel H. wrote:
> One other things comes to mind - whats the relationship between the
> Candelatech's kernel branch and the kvalo's
> https://github.com/kvalo/ath/ ?
> Using the 'main' firmware for ath10k (to support IBSS ad-hoc mode) Im
> not entirely sure which kernel is leading development of the ath10k
> driver.
CT kernels are normally based on upstream (Linus) kernels, but I do sometimes
grab patches from kvalo/ath.
In general, CT kernels have support for some additional features that CT
firmware provides (that are not necessarily available in official ath10k firmware).
>
> Also, is 636 firmware the best / latest / recommended the most for the
> IBSS mode? Or shall I have a look into other version from Candelatech
> / Kvalos repo?
I'm biased, but I think CT firmware would be a better choice that 636,
especially if you can run our CT kernel patches.
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
next prev parent reply other threads:[~2015-09-09 18:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 21:31 WLE600VX from PCEngines Marcel H.
[not found] ` <CABkMH_pegBjg987d5Bs_xkGqk1fsYAZqjSVWorNzPnL_L7PhDw@mail.gmail.com>
2015-09-09 4:10 ` Tomasz Skapski
2015-09-09 5:50 ` Janusz Dziedzic
2015-09-09 6:20 ` Jorge Baranda
2015-09-09 7:43 ` Janusz Dziedzic
2015-09-09 7:49 ` Marcel H.
2015-09-09 9:46 ` Marcel H.
2015-09-09 10:59 ` Harms, Hannes
2015-09-09 11:08 ` Janusz Dziedzic
2015-09-09 11:08 ` [SPAM] " Jorge Baranda
2015-09-09 11:14 ` Ben Greear
2015-09-09 11:15 ` Harms, Hannes
2015-09-09 11:34 ` Marcel H.
2015-09-09 11:40 ` Marcel H.
2015-09-09 18:22 ` Ben Greear [this message]
2015-09-17 10:27 ` [SPAM] " Jorge Baranda
2015-09-17 15:39 ` Jorge Baranda
2015-09-17 16:02 ` Marcel H.
2015-09-17 16:11 ` Ben Greear
2015-09-18 6:29 ` Jorge Baranda
2015-09-09 11:09 ` Janusz Dziedzic
2015-09-09 11:06 ` Janusz Dziedzic
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=55F078E4.2050409@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=maco@blava.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.