From: Sven Eckelmann <sven@open-mesh.com>
To: s prasad <sprasad.kandregula@gmail.com>
Cc: ath10k <ath10k@lists.infradead.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: CT firmware and linux kernel patches for OpenWRT( ar71xx - Tp-Link 1750AC )
Date: Fri, 28 Aug 2015 14:48:02 +0200 [thread overview]
Message-ID: <2249526.TmOlA3g2Uo@bentobox> (raw)
In-Reply-To: <CAJa-X96RZTQ_=dG+PDxu8x_AeMAXhyKiTc7CrNO=hqhnmYAN-Q@mail.gmail.com>
On Wednesday 26 August 2015 18:59:51 s prasad wrote:
> Does anybody have patches for CT firmware testing using OpenWRT environment.
> I tried to create patch, however OpenWRT patches supporting only for
> kernel versions 3.18 and 4.1 at the same time CT Kernels supporting
> 3.17_dev, 4.0.4 and 4.2.x. Both are miss matching.
You have to patch mac80211 and not the kernel. I can give you the patchset
I've used with OpenWrt r46435.
You should get it in the next minutes via private mail (I don't want to
send it over the mailing list due to its size). It is basically the
patchset from Ben put on top of compat-wireless 2015-06-22 [1].
You still need extra changes to get VHT working over IBSS (iw will
otherwise only use HT). When you only want to test it then you can
just hardcode a channel + a channel width in iw's ibss.c.
Kind regards,
Sven
[1] https://dev.cloudtrax.com/git/ath10k-ibss-test.git/shortlog/refs/heads/master-20150824
next prev parent reply other threads:[~2015-08-28 12:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 22:59 CT firmware and linux kernel patches for OpenWRT( ar71xx - Tp-Link 1750AC ) s prasad
2015-08-28 12:48 ` Sven Eckelmann [this message]
[not found] ` <2520663.ftp6yqfzU7@bentobox>
2015-08-31 20:52 ` Fwd: " s prasad
2015-08-31 22:12 ` s prasad
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=2249526.TmOlA3g2Uo@bentobox \
--to=sven@open-mesh.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sprasad.kandregula@gmail.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