From: Kalle Valo <kvalo@kernel.org>
To: Brent Roman <brent@mbari.org>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
linux-wireless@vger.kernel.org,
martin.blumenstingl@googlemail.com
Subject: Re: rtw88 driver support for rtl8723ds does not work on Radxa RockPi-S
Date: Mon, 19 Feb 2024 10:24:45 +0200 [thread overview]
Message-ID: <874je4dfoy.fsf@kernel.org> (raw)
In-Reply-To: <42772df2-32b3-2b37-045d-b528a752bef7@mbari.org> (Brent Roman's message of "Sun, 18 Feb 2024 23:43:19 -0800")
Brent Roman <brent@mbari.org> writes:
> Yes, that's all true. However... Random MAC address assignment tends
> to cause devices to be assigned a different IP address on each reboot.
> This often doesn't play nicely with port forwarding.
Sure, I wasn't claiming that using random addresses is the perfect
solution. But you could also set a fixed random address from user space
(hopefully that works with rtw88).
> It's difficult to "prove" the RK3308 cpu serial numbers are unique,
> but they should be and the few I've tested have been.
Please take into account that rtw88 driver can be used with all sort of
different CPUs, not just RK3308. This is why I pointed this out.
(please don't top post)
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-02-19 8:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 23:55 rtw88 driver support for rtl8723ds does not work on Radxa RockPi-S Brent Roman
2024-02-16 17:36 ` Larry Finger
2024-02-18 5:13 ` Brent Roman
2024-02-18 15:55 ` Larry Finger
2024-02-19 6:28 ` Kalle Valo
2024-02-19 7:43 ` Brent Roman
2024-02-19 8:24 ` Kalle Valo [this message]
2024-02-19 8:31 ` Brent Roman
2024-02-19 15:40 ` Larry Finger
2024-02-19 16:03 ` Kalle Valo
-- strict thread matches above, loose matches on Subject: below --
2024-02-02 5:14 Brent Roman
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=874je4dfoy.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=Larry.Finger@lwfinger.net \
--cc=brent@mbari.org \
--cc=linux-wireless@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).