Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: Linux-OMAP <linux-omap@vger.kernel.org>,
	linux-wireless@vger.kernel.org,
	sebastian.reichel@collabora.co.uk, Eyal Reizer <eyalr@ti.com>
Subject: Re: wl18xx: NVS file handling
Date: Thu, 21 Apr 2022 08:19:08 +0300	[thread overview]
Message-ID: <YmDpTAu9wmlLijDA@atomide.com> (raw)
In-Reply-To: <CAGm1_ktEim1vGOf5i=H_sqrPvg=dT50790YYwXgYKgAut-a=ng@mail.gmail.com>

Hi,

* Yegor Yefremov <yegorslists@googlemail.com> [220420 13:58]:
> Hi all,
> 
> using the 5.18.x kernel, I get the following warning:
> 
> wlcore: WARNING Detected unconfigured mac address in nvs, derive from
> fuse instead.
> wlcore: WARNING This default nvs file can be removed from the file system
> 
> removing the /lib/firmware/ti-connectivity/wl127x-nvs.bin file, I get
> this warning:
> 
> wl18xx_driver wl18xx.0.auto: Direct firmware load for
> ti-connectivity/wl1271-nvs.bin failed with error -2
> 
> What's the best way to get rid of these warnings when I don't want to
> handle WLAN's MAC address via the wl127x-nvs.bin?

See commit d382b9c00782 ("wlcore: add missing nvs file name info for
wilink8"), to me looks like the the second warning should be just removed
for wl18xx.

> According to this discussion [1], NVS file is the last resort for
> handling the MAC address.
> 
> [1] https://patchwork.kernel.org/project/linux-wireless/patch/8665E2433BC68541A24DFFCA87B70F5B363E1A3D@DFRE01.ent.ti.com/

Yes the NVS file does not work at all for NFSroot for multiple devices.

To me it seems we should have the option for the MAC address to be
populated by the bootloader for the devicetree property like Ethernet
adapters typically do. Not sure what that might take, maybe it
already works. I guess the first step would be to make the nvs file
completely optional for wlcore.

Regards,

Tony



  reply	other threads:[~2022-04-21  5:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-20 13:57 wl18xx: NVS file handling Yegor Yefremov
2022-04-21  5:19 ` Tony Lindgren [this message]
2022-04-21  9:01   ` Yegor Yefremov
2022-04-22 10:43     ` Yegor Yefremov
2022-04-22 12:08       ` Tony Lindgren
2022-04-22 12:34         ` Yegor Yefremov
2022-04-23  6:16         ` Kalle Valo
2022-04-25  6:43           ` Yegor Yefremov

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=YmDpTAu9wmlLijDA@atomide.com \
    --to=tony@atomide.com \
    --cc=eyalr@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sebastian.reichel@collabora.co.uk \
    --cc=yegorslists@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