linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Brent Roman <brent@mbari.org>,
	 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 08:28:41 +0200	[thread overview]
Message-ID: <878r3hc6hy.fsf@kernel.org> (raw)
In-Reply-To: <b9a4df4e-4b1f-436f-ae4b-90fc0c68ae81@lwfinger.net> (Larry Finger's message of "Sun, 18 Feb 2024 09:55:59 -0600")

Larry Finger <Larry.Finger@lwfinger.net> writes:

> On 2/17/24 23:13, Brent Roman wrote:
>> Larry,
>> Radxa confirmed that they do not program the eFUSE on these boards.
>> We do not get a sensible MAC from the chip, so I derive a one from
>> the CPU's unique serial number.
>> It's a hack, but it works well and is standard's compliant.
>> The RockPI-S a *very* inexpensive board, so I can understand Radxa
>> wanting to minimize the time spent configuring each one.
>> https://shop.allnetchina.cn/products/rock-pi-s
>> The vendor driver seems to deal with this by applying typical gain
>> parameters when the eFUSE is invalid.
>> With that driver, this board's WiFi performs beautifully, despite
>> the unprogrammed eFUSE.
>> Would you accept a patch to add this logic to RTW88?
>
> Of course a patch would be accepted. Ultimately, the changes should be
> made to the wireless-next code base, and sent to this mailing list. To
> make things easier, you can send me a patch file for the rtw88 repo,
> and I can reformat it for wireless-next and send it to the mailing
> list under your signed-off-by. Either one would work.
>
> Thanks for sorting this out. I like the idea of deriving the MAC
> address from the CPU serial number. That is unique and reproducible.

But make sure that the CPU serial number is really unique. If it's not
that can cause MAC address collisions which is not good.

Usually wireless drivers create a random address if a stored MAC address
is not available.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2024-02-19  6:28 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 [this message]
2024-02-19  7:43         ` Brent Roman
2024-02-19  8:24           ` Kalle Valo
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=878r3hc6hy.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).