Received-SPF: softfail (google.com: domain of transitioning linux-wireless-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19;
MIME-Version: 1.0
References: <CAGm1_ktEim1vGOf5i=H_sqrPvg=dT50790YYwXgYKgAut-a=ng@mail.gmail.com>
 <YmDpTAu9wmlLijDA@atomide.com> <CAGm1_kv+b1h1OuWr4w5jS_mqfQpXF7UexiWFsOSs+MJK546=ew@mail.gmail.com>
 <CAGm1_ksOt-JtOcTBG7wEqaHagx1NTGYXTMTOG40AN2RELqWKwg@mail.gmail.com> <YmKaoRfxo4bMzDdR@atomide.com>
In-Reply-To: <YmKaoRfxo4bMzDdR@atomide.com>
From:   Yegor Yefremov <yegorslists@googlemail.com>
Date:   Fri, 22 Apr 2022 14:34:31 +0200
Message-ID: <CAGm1_ktc0OsYEt-D=OUhEJz6VFgW15wBWkxb6fS5CWTgzZ6YHg@mail.gmail.com>
Subject: Re: wl18xx: NVS file handling
To:     Tony Lindgren <tony@atomide.com>
Cc:     Linux-OMAP <linux-omap@vger.kernel.org>,
        linux-wireless@vger.kernel.org, sebastian.reichel@collabora.co.uk
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Fri, Apr 22, 2022 at 2:08 PM Tony Lindgren <tony@atomide.com> wrote:
>
> * Yegor Yefremov <yegorslists@googlemail.com> [220422 10:40]:
> > Wouldn't we need this functionality [1] to make the NVS fw file optional? :-(
> >
> > [1] https://patchwork.kernel.org/project/linux-dmaengine/patch/20181112160143.4459-1-l.stach@pengutronix.de/
>
> Hmm yeah, how about if we use just an empty nvs file for no warnings then?

touch /lib/firmware/ti-connectivity/wl1271-nvs.bin

wl18xx_driver wl18xx.0.auto: loading
/lib/firmware/ti-connectivity/wl1271-nvs.bin failed with error -22
wl18xx_driver wl18xx.0.auto: Direct firmware load for
ti-connectivity/wl1271-nvs.bin failed with error -22

Regards,
Yegor