Received: by 2002:a05:6a10:6d10:0:0:0:0 with SMTP id gq16csp535629pxb; Fri, 22 Apr 2022 06:23:08 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy5ZjoxXZ4E7QKtSWGap3RytD8X6kPFt6OIMvY2xf8CPiMZK4VrP+VTnAVy5xjBSeXJPNBb X-Received: by 2002:a05:6808:2123:b0:322:79b9:9c1 with SMTP id r35-20020a056808212300b0032279b909c1mr6300121oiw.222.1650633788651; Fri, 22 Apr 2022 06:23:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1650633788; cv=none; d=google.com; s=arc-20160816; b=OklsEMWeBLexQZaMz9XhmBFil4pdvgESxBGfeflpwsoBzpqE0npOE9Q25jrBft52Cw bwQNz7X2wQuj6o+WBUNr4fQGYjVqw1gmfcBN9qa1R5Udu65HtRyD3Znp6dPisjIk4vYg FDkSTrBFRSdhHDXRzasQgdft6ryhcE3/WspXp49L92HCG9ELjSqbTgEksovTRnuK439j KyXIpYaOF5+lUVl53YlZYrtW2EoppCeJGnWrnb4+TvFh+kaP13sMj1MBP48ffV+oQdnT vLnMLDPT1mGxlxhnyj5oxk5xGc73JSs3apkjWykAJvOi0qM174ZGV9dCBltneslTOklo gQlg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=BesJbNfSZMn9xvvNnMiRjyxCRQX/ltpgV7ZRnugWBpw=; b=ZK5ZrBDdPh6jp5bkCXOTyyZLIQ86LyLflpTaXweCE2SyIIJCNG2+z2Hn2GGRjuHS19 HVolZwF4Xpm3D2LHUkgHpC/DGt+x6e0jbBJ0jZYHPjHquyyW57jY9mLLNru1EPQ6jCV4 3ule3Xp9Ki304cYQDBFfAxEY38skSSSEYw1Aimttx57L+/FV3OaBPPLH+zjTHqH2bHc/ awV34rvmLSu5f5Ea7CKHL3YqmdffR4PWj9ttyS+1IeoxFG5C2/pRpbnbhN2ZGLZSrxmX o2rKJE7kFZH4zJmN0hMqpvBFILp5w49PSM6xiHq2LG1zHMiDG6D9WyBeeSlcKTCfSVGv XX2A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id a4-20020a056808120400b0032293379065si4625248oil.219.2022.04.22.06.22.50; Fri, 22 Apr 2022 06:23:08 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1377199AbiDUFWB (ORCPT + 67 others); Thu, 21 Apr 2022 01:22:01 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54566 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233065AbiDUFWA (ORCPT ); Thu, 21 Apr 2022 01:22:00 -0400 Received: from muru.com (muru.com [72.249.23.125]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 55B4DC7C; Wed, 20 Apr 2022 22:19:10 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id 92A19811B; Thu, 21 Apr 2022 05:16:18 +0000 (UTC) Date: Thu, 21 Apr 2022 08:19:08 +0300 From: Tony Lindgren To: Yegor Yefremov Cc: Linux-OMAP , linux-wireless@vger.kernel.org, sebastian.reichel@collabora.co.uk, Eyal Reizer Subject: Re: wl18xx: NVS file handling Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org Hi, * Yegor Yefremov [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