Skip to contentSkip to conversation

ath10k: qca6174 firmware: difference between hw2.1/firmware-5 and hw3.0/firmware-4

DISCUSSION Xuebing Wang 3 participants 8 messages Aug 24, 2016 – Sep 8, 2016 Qualcomm Atheros ATH10K wireless driver

lore
Share & tools
lore
#0 lore raw

Hi Kalle,

I cloned your ath10k-firmware from your github. Would you please advise what are the differences of hw2.1/firmware-5 and hw3.0/firmware-4 for qca6174? Does hw3.0/firmware-4 support Monitor Mode?

I have a wlan card with BMI version (QCA6174_HW_2_1_VERSION 0x05010000) and Monitor Mode works no problem with latest kernel v4.8-rc2.

I have another wlan card with (QCA6174_HW_3_2_VERSION 0x05030000). I am trying to back-port ath10k from v4.8-rc2 to 3.10.73 for this HW_3_2 QCA6174 wlan card. Virtual interface (mon0) can be added and brought-up, but tcpdump can not capture any packets. I am wondering if it could be related to (hw2.1/firmware-5 vs hw3.0/firmware-4)?

I can not try v4.8-rc2 for this HW_3_2 wlan card, because it is used in an android phone.

Thanks a lot for your help.

Signature · 6 lines
Xuebing

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k
#1 lore raw
Quoted 6 lines · Xuebing Wang

Hi Kalle,

I cloned your ath10k-firmware from your github. Would you please advise what are the differences of hw2.1/firmware-5 and hw3.0/firmware-4 for qca6174? Does hw3.0/firmware-4 support Monitor Mode?

Quoted 8 lines

I have a wlan card with BMI version (QCA6174_HW_2_1_VERSION 0x05010000) and Monitor Mode works no problem with latest kernel v4.8-rc2.

I have another wlan card with (QCA6174_HW_3_2_VERSION 0x05030000). I am trying to back-port ath10k from v4.8-rc2 to 3.10.73 for this HW_3_2 QCA6174 wlan card. Virtual interface (mon0) can be added and brought-up, but tcpdump can not capture any packets. I am wondering if it could be related to (hw2.1/firmware-5 vs hw3.0/firmware-4)?

Official hw3.x's firmware supports full rx offload. Rx event used to deliver frames is very specialized effectively preventing sniffing / monitor operation.

I don't know if there's any way around it without getting your hands on firmware build that doesn't have the full rx offload compiled in (assuming such a build even exists).

Michał

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k

#2 lore raw

Hi Michal, thanks.

Hi Kalle,

Is there a version of hw3.0 firmware (without Rx offloading) for me to give a try of Monitor Mode on qca6174 hw3.2 chip? Thanks.

xuebing

Quoted 26 lines · Michal Kazior
Quoted 6 lines · Xuebing Wang

Hi Kalle,

I cloned your ath10k-firmware from your github. Would you please advise what are the differences of hw2.1/firmware-5 and hw3.0/firmware-4 for qca6174? Does hw3.0/firmware-4 support Monitor Mode?

Quoted 8 lines

I have a wlan card with BMI version (QCA6174_HW_2_1_VERSION 0x05010000) and Monitor Mode works no problem with latest kernel v4.8-rc2.

I have another wlan card with (QCA6174_HW_3_2_VERSION 0x05030000). I am trying to back-port ath10k from v4.8-rc2 to 3.10.73 for this HW_3_2 QCA6174 wlan card. Virtual interface (mon0) can be added and brought-up, but tcpdump can not capture any packets. I am wondering if it could be related to (hw2.1/firmware-5 vs hw3.0/firmware-4)?

Official hw3.x's firmware supports full rx offload. Rx event used to deliver frames is very specialized effectively preventing sniffing / monitor operation.

I don't know if there's any way around it without getting your hands on firmware build that doesn't have the full rx offload compiled in (assuming such a build even exists).

Michał

Signature · 6 lines
Xuebing

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k
#3 lore raw

Hi Michal, Stanislaw and community,

Are you aware of any WLAN card with qca6174 hw3.2 chip (BMI version signatures = 0x05030000 = QCA6174_HW_3_2_VERSION), so I can buy one to test on Linux PC with upstream kernel, to ensure hw3.0 firmware (not hw2.1 firmware) (hopefully without Rx offloading) works with Monitor Mode?

Thanks.

xuebing

Quoted 37 lines · Xuebing Wang

Hi Michal, thanks.

Hi Kalle,

Is there a version of hw3.0 firmware (without Rx offloading) for me to give a try of Monitor Mode on qca6174 hw3.2 chip? Thanks.

xuebing

Quoted 26 lines · Michal Kazior
Quoted 6 lines · Xuebing Wang

Hi Kalle,

I cloned your ath10k-firmware from your github. Would you please advise what are the differences of hw2.1/firmware-5 and hw3.0/firmware-4 for qca6174? Does hw3.0/firmware-4 support Monitor Mode?

Quoted 8 lines

I have a wlan card with BMI version (QCA6174_HW_2_1_VERSION 0x05010000) and Monitor Mode works no problem with latest kernel v4.8-rc2.

I have another wlan card with (QCA6174_HW_3_2_VERSION 0x05030000). I am trying to back-port ath10k from v4.8-rc2 to 3.10.73 for this HW_3_2 QCA6174 wlan card. Virtual interface (mon0) can be added and brought-up, but tcpdump can not capture any packets. I am wondering if it could be related to (hw2.1/firmware-5 vs hw3.0/firmware-4)?

Official hw3.x's firmware supports full rx offload. Rx event used to deliver frames is very specialized effectively preventing sniffing / monitor operation.

I don't know if there's any way around it without getting your hands on firmware build that doesn't have the full rx offload compiled in (assuming such a build even exists).

Michał

Signature · 6 lines
Xuebing

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k
#4 lore raw
In reply to Xuebing Wang
Quoted 4 lines · Xuebing Wang

Hi Kalle,

Is there a version of hw3.0 firmware (without Rx offloading) for me to give a try of Monitor Mode on qca6174 hw3.2 chip? Thanks.

I haven't heard anything like that, most likely not. But I'm no firmware expert.

Signature · 5 lines
Kalle Valo
_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k
#5 lore raw
In reply to Michal Kazior
Quoted 19 lines · Michal Kazior
Quoted 6 lines · Xuebing Wang

Hi Kalle,

I cloned your ath10k-firmware from your github. Would you please advise what are the differences of hw2.1/firmware-5 and hw3.0/firmware-4 for qca6174? Does hw3.0/firmware-4 support Monitor Mode?

Quoted 8 lines

I have a wlan card with BMI version (QCA6174_HW_2_1_VERSION 0x05010000) and Monitor Mode works no problem with latest kernel v4.8-rc2.

I have another wlan card with (QCA6174_HW_3_2_VERSION 0x05030000). I am trying to back-port ath10k from v4.8-rc2 to 3.10.73 for this HW_3_2 QCA6174 wlan card. Virtual interface (mon0) can be added and brought-up, but tcpdump can not capture any packets. I am wondering if it could be related to (hw2.1/firmware-5 vs hw3.0/firmware-4)?

Official hw3.x's firmware supports full rx offload. Rx event used to deliver frames is very specialized effectively preventing sniffing / monitor operation.

Quoted 6 lines

I don't know if there's any way around it without getting your hands on firmware build that doesn't have the full rx offload compiled in (assuming such a build even exists).

Michał

Hi Michal,

I confirm hw3.0 firmware does not support monitor mode, on kernel 4.8.0-rc2.

I got one Killer 1535 wlan card (with qca6174 hw3.2), monitor mode does not work. I do use monitor mode on hw2.1 qca6174 and ath9k many times.

dmesg shows:
------
qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:1535
kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5 board_file api 2 bmi_id N/A crc32 46b57247
------

Also, I can not set hw3.x firmware monitor mode to a specific freq as below. I am using Ubuntu 16.04.1 with kernel 4.8.0-rc2.
------

$ sudo iw dev mon0 set freq 2462
$ iwconfig mon0
mon0      IEEE 802.11  Mode:Monitor  Tx-Power=0 dBm
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:on
------

HI Kalle,

Do you consider this hw3.0 firmware does not support monitor mode a firmware bug?

Thanks.

Signature · 6 lines
Xuebing

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k
#6 lore raw
Quoted 51 lines · Xuebing Wang
Quoted 19 lines · Michal Kazior
Quoted 6 lines · Xuebing Wang

Hi Kalle,

I cloned your ath10k-firmware from your github. Would you please advise what are the differences of hw2.1/firmware-5 and hw3.0/firmware-4 for qca6174? Does hw3.0/firmware-4 support Monitor Mode?

Quoted 8 lines

I have a wlan card with BMI version (QCA6174_HW_2_1_VERSION 0x05010000) and Monitor Mode works no problem with latest kernel v4.8-rc2.

I have another wlan card with (QCA6174_HW_3_2_VERSION 0x05030000). I am trying to back-port ath10k from v4.8-rc2 to 3.10.73 for this HW_3_2 QCA6174 wlan card. Virtual interface (mon0) can be added and brought-up, but tcpdump can not capture any packets. I am wondering if it could be related to (hw2.1/firmware-5 vs hw3.0/firmware-4)?

Official hw3.x's firmware supports full rx offload. Rx event used to deliver frames is very specialized effectively preventing sniffing / monitor operation.

Quoted 6 lines

I don't know if there's any way around it without getting your hands on firmware build that doesn't have the full rx offload compiled in (assuming such a build even exists).

Michał

Hi Michal,

I confirm hw3.0 firmware does not support monitor mode, on kernel 4.8.0-rc2.

I got one Killer 1535 wlan card (with qca6174 hw3.2), monitor mode does not work. I do use monitor mode on hw2.1 qca6174 and ath9k many times.

dmesg shows:
------
qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:1535
kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5 board_file api 2 bmi_id N/A crc32 46b57247
------

Also, I can not set hw3.x firmware monitor mode to a specific freq as below. I am using Ubuntu 16.04.1 with kernel 4.8.0-rc2.
------

$ sudo iw dev mon0 set freq 2462
$ iwconfig mon0
mon0      IEEE 802.11  Mode:Monitor  Tx-Power=0 dBm
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:on
------
Quoted 5 lines

HI Kalle,

Do you consider this hw3.0 firmware does not support monitor mode a firmware bug?

Thanks.

Hi Kalle,

For unknown reasons, previous email bounced back. It did successfully went to ath10k mailing list.

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.

Signature · 6 lines
Xuebing

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k
#7 lore raw
Quoted 7 lines · Xuebing Wang
Quoted 4 lines

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.

Quoted 3 lines

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.

Signature · 5 lines
Kalle Valo
_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k