From: Ben Greear <greearb@candelatech.com>
To: s prasad <sprasad.kandregula@gmail.com>
Cc: Michal Kazior <michal.kazior@tieto.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
Kalle Valo <kvalo@qca.qualcomm.com>
Subject: Re: Ath10 firmware crashing in Monitor mode(Sniffer mode)
Date: Thu, 13 Aug 2015 13:43:34 -0700 [thread overview]
Message-ID: <55CD0176.5080003@candelatech.com> (raw)
In-Reply-To: <CAJa-X97Av+FKwy5Q3x3jnC=KPmqFt_JfsaVQ6J3bScM-SEKnYg@mail.gmail.com>
On 08/13/2015 01:35 PM, s prasad wrote:
> Hi Ben,
>
> did you get a chance to look into this issue(injecting frames when
> device in monitor mode).
Injection works in a limited fashion in my latest firmware.
I'd like to figure out how to pass rate-ctrl (and other info?) down to the
firmware on a per-pkt basis..but I don't see a way yet.
Probably I have to hack the htt header or something like that
to give some extra space. That sort of thing might allow a host-based
rate-ctrl algorithm to be used....if someone is interested in working on
the driver/kernel side of things for this effort let me know.
I am not aware of any crashes related to monitor mode in my
firmware..but if you can crash it, send me the crash dump and
I'll take a look.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2015-08-13 20:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-10 20:56 Ath10 firmware crashing in Monitor mode(Sniffer mode) s prasad
2015-05-11 5:50 ` Michal Kazior
2015-05-11 10:51 ` s prasad
2015-05-11 11:08 ` Michal Kazior
[not found] ` <CAJa-X96KPw6dY0pK1zc8UD4TdQcG0KuA3m6DSueVVyK-VPhn9g@mail.gmail.com>
2015-05-12 5:03 ` Michal Kazior
2015-05-12 9:31 ` s prasad
2015-05-12 10:14 ` Michal Kazior
2015-05-12 14:41 ` Ben Greear
2015-05-12 15:08 ` s prasad
2015-08-13 20:35 ` s prasad
2015-08-13 20:43 ` Ben Greear [this message]
2015-08-13 21:01 ` S Prasad Kandregula
2015-08-14 15:57 ` Ben Greear
2015-05-12 12:19 ` Kalle Valo
2015-05-12 12:34 ` Michal Kazior
2015-05-12 12:53 ` Kalle Valo
2015-05-11 8:52 ` Mário Lopes
2015-05-11 9:14 ` Michal Kazior
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=55CD0176.5080003@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.com \
--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;
as well as URLs for NNTP newsgroup(s).