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:19:17 +0300 [thread overview]
Message-ID: <87iobygf96.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CA+BoTQ=bqHPrdgGVfSfdJa5vobDBRdxRwMR_wJzUj4Z9WjotoQ@mail.gmail.com> (Michal Kazior's message of "Tue, 12 May 2015 07:03:42 +0200")
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?
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: s prasad <sprasad.kandregula@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: Ath10 firmware crashing in Monitor mode(Sniffer mode)
Date: Tue, 12 May 2015 15:19:17 +0300 [thread overview]
Message-ID: <87iobygf96.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CA+BoTQ=bqHPrdgGVfSfdJa5vobDBRdxRwMR_wJzUj4Z9WjotoQ@mail.gmail.com> (Michal Kazior's message of "Tue, 12 May 2015 07:03:42 +0200")
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?
--
Kalle Valo
next prev parent reply other threads:[~2015-05-12 12:19 UTC|newest]
Thread overview: 36+ 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-10 20:56 ` s prasad
2015-05-11 5:50 ` Michal Kazior
2015-05-11 5:50 ` Michal Kazior
2015-05-11 10:51 ` s prasad
2015-05-11 10:51 ` s prasad
2015-05-11 11:08 ` Michal Kazior
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 5:03 ` Michal Kazior
2015-05-12 9:31 ` s prasad
2015-05-12 9:31 ` s prasad
2015-05-12 10:14 ` Michal Kazior
2015-05-12 10:14 ` Michal Kazior
2015-05-12 14:41 ` Ben Greear
2015-05-12 14:41 ` Ben Greear
2015-05-12 15:08 ` s prasad
2015-05-12 15:08 ` s prasad
2015-08-13 20:35 ` s prasad
2015-08-13 20:35 ` s prasad
2015-08-13 20:43 ` Ben Greear
2015-08-13 20:43 ` Ben Greear
2015-08-13 21:01 ` S Prasad Kandregula
2015-08-13 21:01 ` S Prasad Kandregula
2015-08-14 15:57 ` Ben Greear
2015-08-14 15:57 ` Ben Greear
2015-05-12 12:19 ` Kalle Valo [this message]
2015-05-12 12:19 ` Kalle Valo
2015-05-12 12:34 ` Michal Kazior
2015-05-12 12:34 ` Michal Kazior
2015-05-12 12:53 ` Kalle Valo
2015-05-12 12:53 ` Kalle Valo
2015-05-11 8:52 ` Mário Lopes
2015-05-11 8:52 ` Mário Lopes
2015-05-11 9:14 ` Michal Kazior
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=87iobygf96.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 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.