All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: "raspberrykan@stu.hqu.edu.cn" <raspberrykan@stu.hqu.edu.cn>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] wifi: rtw88: use firmware MAC address as fallback
Date: Wed, 2 Sep 2026 02:33:44 +0000	[thread overview]
Message-ID: <57178758e2d9499c9582d4bcf821f2fe@realtek.com> (raw)
In-Reply-To: <SEZPR04MB617269B16E24E662180A7678FFB72@SEZPR04MB6172.apcprd04.prod.outlook.com>

(Please in plain text and not top posting)

raspberrykan@stu.hqu.edu.cn <raspberrykan@stu.hqu.edu.cn>  wrote:
> > Please share the board and WiFi chip you are using.
> The board is a Xiaomi Mi Box 4 based on the Amlogic S905L SoC, and the
> WiFi chip is an RTL8723DS.
> On this device, the actual WiFi MAC address is stored in the S905L
> SoC's eFuse rather than in the RTL8723DS efuse. The platform firmware
> provides this MAC address to the device, so I am using
> device_get_mac_address() as a fallback when the MAC address read by
> rtw88 is invalid.

Please share it in commit message.

> The kernel tree I used for testing is also available here:
> https://github.com/Raspberry-Monster/linux

I see the top commit of [1]. The mac_ret is also missed. How can you
test it?

[1] https://github.com/Raspberry-Monster/linux/commits/rtw88-dt-mac/


  parent reply	other threads:[~2026-09-02  2:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-01 12:45 [PATCH] wifi: rtw88: use firmware MAC address as fallback YuChia-Kan
2026-09-02  1:22 ` Ping-Ke Shih
     [not found]   ` <SEZPR04MB617269B16E24E662180A7678FFB72@SEZPR04MB6172.apcprd04.prod.outlook.com>
2026-09-02  2:33     ` Ping-Ke Shih [this message]
2026-09-02  3:10       ` 回复: " raspberrykan
2026-09-02  2:46 ` [PATCH v2] " YuChia-Kan
2026-09-02  3:14   ` [PATCH v3] " YuChia-Kan
2026-09-07  2:43     ` Ping-Ke Shih
2026-09-08  2:50     ` Ping-Ke Shih

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=57178758e2d9499c9582d4bcf821f2fe@realtek.com \
    --to=pkshih@realtek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=raspberrykan@stu.hqu.edu.cn \
    /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.