From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
s prasad <sprasad.kandregula@gmail.com>
Subject: Re: Ath10 firmware crashing in Monitor mode(Sniffer mode)
Date: Tue, 12 May 2015 15:53:22 +0300 [thread overview]
Message-ID: <87bnhqgdod.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CA+BoTQkduFA78B70hyn9FNbyKX_Yd=9cH9notfEC93Owm9sRSg@mail.gmail.com> (Michal Kazior's message of "Tue, 12 May 2015 14:34:57 +0200")
Michal Kazior <michal.kazior@tieto.com> writes:
> On 12 May 2015 at 14:19, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
>> Michal Kazior <michal.kazior@tieto.com> writes:
>>
>>> On 11 May 2015 at 23:27, s prasad <sprasad.kandregula@gmail.com> wrote:
>>>> Tested as you suggested, however didn't help. Please find attached log
>>>> files for each firmware type.
>>>>
>>>> While executing following commands in sequence, captured dmesg. I hope
>>>> those logs will help. If not please let me know.
>>>
>>> Thanks!
>>>
>>> Apparently I've missed from your original email the fact that you're
>>> trying to inject packets. This isn't supported in ath10k.
>>
>> IMHO we should somehow warn the user or prevent that happening. Is there
>> a way to do that?
>
> We could add an extra condition in ath10k_tx() to drop/free packets
> immediately and warn if an injection attempt is made.
Yeah, that would be really good to have.
--
Kalle Valo
next prev parent reply other threads:[~2015-05-12 12:53 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
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 [this message]
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=87bnhqgdod.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--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).