From: Ben Greear <greearb@candelatech.com>
To: Bob Copeland <me@bobcopeland.com>,
Yeoh Chun-Yeow <yeohchunyeow@gmail.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: attempting mesh on ath10k
Date: Tue, 28 Apr 2015 07:47:56 -0700 [thread overview]
Message-ID: <553F9D9C.9080004@candelatech.com> (raw)
In-Reply-To: <20150428125748.GE4527@localhost>
On 04/28/2015 05:57 AM, Bob Copeland wrote:
> On Tue, Apr 28, 2015 at 08:50:01PM +0800, Chun-Yeow Yeoh wrote:
>> Great works, Bob.
>>
>> Which AP firmware that you have tested with?
>
> That is with:
>
> [ 16.670000] ath10k_pci 0000:01:00.0: qca988x hw2.0 (0x4100016c,
> 0x043202ff) fw 10.2.4.45 api 4 htt 2.1 wmi 5 cal otp max_sta 128
>
> I think it should work with CT too. I need to go back and validate
> that, and also make sure I can repro the AID crash on CT. A confounding
> factor is that every time I build new drivers for OpenWRT, it overwrites
> the firmware again...
If you feel adventurous, and want to apply some of my ath10k patches,
I have a way to dump some of the interesting registers in CT firmware,
including the rx-filter register.
Maybe I can figure out what needs to be twiddled w/out having to add
a monitor device.
I could also potentially add a vdev type or flag for mesh interface,
but that would definitely require driver hacks to enable the new
flag and it would not be compatible with other upstream firmware.
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-04-28 14:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 12:50 attempting mesh on ath10k Bob Copeland
2015-04-24 17:55 ` Yeoh Chun-Yeow
2015-04-25 1:38 ` Ben Greear
2015-04-26 14:15 ` Bob Copeland
2015-04-26 15:42 ` Ben Greear
2015-04-27 13:00 ` Bob Copeland
2015-04-28 5:47 ` Michal Kazior
2015-04-28 12:25 ` Bob Copeland
2015-05-27 6:51 ` Bartosz Markowski
2015-05-27 11:12 ` Bob Copeland
2015-05-27 11:15 ` Bartosz Markowski
2015-04-28 12:41 ` Bob Copeland
2015-04-28 12:50 ` Yeoh Chun-Yeow
2015-04-28 12:57 ` Bob Copeland
2015-04-28 14:47 ` Ben Greear [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-07-06 21:25 Freddy Lee
2015-07-06 21:49 ` Bob Copeland
2015-07-06 21:54 ` Bob Copeland
2015-07-12 14:25 ` Bob Copeland
2015-07-13 1:43 ` Bob Copeland
2015-07-13 8:13 ` Michal Kazior
2015-07-13 10:57 ` Bob Copeland
2015-07-20 13:57 ` Bob Copeland
2015-08-13 3:14 ` Bob Copeland
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=553F9D9C.9080004@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=me@bobcopeland.com \
--cc=yeohchunyeow@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 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.