From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: Xuebing Wang <xbing6@gmail.com>
Cc: "michal.kazior@tieto.com" <michal.kazior@tieto.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: ath10k: qca6174 firmware: difference between hw2.1/firmware-5 and hw3.0/firmware-4
Date: Thu, 8 Sep 2016 05:13:08 +0000 [thread overview]
Message-ID: <877fanug7w.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <8e4afd35-9216-acf7-adb7-404976a5cc12@gmail.com> (Xuebing Wang's message of "Thu, 8 Sep 2016 07:25:57 +0800")
Xuebing Wang <xbing6@gmail.com> writes:
>> Do you consider this hw3.0 firmware does not support monitor mode a
>> firmware bug?
>>
>> Thanks.
>
> For unknown reasons, previous email bounced back. It did successfully
> went to ath10k mailing list.
I did get it, I just didn't have a chance to reply yet.
> Do you consider this hw3.0 firmware does not support monitor mode a
> firmware bug, or do you see any chance to add a way to configure
> firmware to enable Monitor Mode? Thanks.
Not a bug but more like QCA6174 firmware is missing a very useful
feature. But my opinion doesn't really matter here as I'm not part of
the firmware team, I just deliver their releases. The firmware team
makes the decisions what features include to their releases.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2016-09-08 5:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 3:57 ath10k: qca6174 firmware: difference between hw2.1/firmware-5 and hw3.0/firmware-4 Xuebing Wang
2016-08-24 6:13 ` Michal Kazior
2016-08-24 9:11 ` Xuebing Wang
2016-08-24 9:57 ` Xuebing Wang
2016-08-30 8:03 ` Valo, Kalle
2016-09-05 2:56 ` Xuebing Wang
2016-09-07 23:25 ` Xuebing Wang
2016-09-08 5:13 ` Valo, Kalle [this message]
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=877fanug7w.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=michal.kazior@tieto.com \
--cc=xbing6@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.