From: Sven Eckelmann <sven@narfation.org>
To: ath11k@lists.infradead.org
Subject: IPQ8074: hw2.0: Wrong mac address for 2.4GHz PHY with firmware 2.5.0.1.r1-00004
Date: Mon, 18 Jan 2021 09:14:54 +0100 [thread overview]
Message-ID: <12396947.EVyyLHbfrO@ripper> (raw)
[already send this last week but mime messages seem to be blocked on this ml]
Hi,
I have here a device which was previously using the firmware
WLAN.HK.2.4.0.1.r1-00026-QCAHKSWPL_SILICONZ-2. It has a ath10k radio for
scanning (phy0), an ath11k 5GHz radio0 (phy1) and a 2.4GHz radio (phy2).
/sys/class/ieee80211/phy0/macaddress:f8:d9:b8:2e:36:c4 (ath10k)
/sys/class/ieee80211/phy1/macaddress:f8:d9:b8:2e:36:d0
/sys/class/ieee80211/phy2/macaddress:f8:d9:b8:2e:37:c8
Now with the new firmware WLAN.HK.2.5.0.1.r1-00004-QCAHKSWPL_SILICONZ-1, it
suddenly uses a mac address which is not part of the pre-cal data.
/sys/class/ieee80211/phy0/macaddress:f8:d9:b8:2e:36:c4 (ath10k)
/sys/class/ieee80211/phy1/macaddress:f8:d9:b8:2e:36:d0
/sys/class/ieee80211/phy2/macaddress:f8:d9:b8:2e:37:d0
This odd behavior causes layer 2 (mac) address conflicts - which should never
ever happen.
The device was just performed a cold boot and I have no idea why the firmware
reports this mac address. But the caldata is attached for further inspection
to the next mail (which Kalle has to approve manually).
It has following set
* first mac (COMMON_BDF_HEADER.baseBdfHeader.macAddr[0]): f8:d9:b8:2e:36:d0
* second mac (COMMON_BDF_HEADER.baseBdfHeader.macAddr[1]): f8:d9:b8:2e:36:c8
* number macs (COMMON_BDF_HEADER.baseBdfHeader.numMacAddr): 2
* mac flag (COMMON_BDF_HEADER.baseBdfHeader.nvMacFlag): 1
Kind regards,
Sven
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next reply other threads:[~2021-01-18 8:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 8:14 Sven Eckelmann [this message]
2021-01-18 8:15 ` IPQ8074: hw2.0: Wrong mac address for 2.4GHz PHY with firmware 2.5.0.1.r1-00004 Sven Eckelmann
2021-01-19 15:56 ` Sven Eckelmann
2021-03-01 9:46 ` Sven Eckelmann
2021-03-01 10:19 ` Sven Eckelmann
2021-03-01 10:58 ` Kalle Valo
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=12396947.EVyyLHbfrO@ripper \
--to=sven@narfation.org \
--cc=ath11k@lists.infradead.org \
/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