Return-path: Received: from mail-wi0-f181.google.com ([209.85.212.181]:44547 "EHLO mail-wi0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752481AbaLHTmT (ORCPT ); Mon, 8 Dec 2014 14:42:19 -0500 Message-ID: <5485FF17.1070504@gmail.com> (sfid-20141208_204238_795015_1FE0269A) Date: Mon, 08 Dec 2014 21:42:15 +0200 From: Ivaylo Dimitrov MIME-Version: 1.0 To: Dan Williams , =?UTF-8?B?UGFsaSBSb2jDoXI=?= CC: Marcel Holtmann , Greg Kroah-Hartman , Ming Lei , Pavel Machek , "John W. Linville" , Grazvydas Ignotas , "linux-wireless@vger.kernel.org" , Network Development , Linux Kernel Mailing List , Aaro Koskinen , Kalle Valo , Sebastian Reichel , David Gnedt Subject: Re: wl1251: NVS firmware data References: <201411271506.20457@pali> <201412081811.46943@pali> <30072B9E-2495-4F90-AC91-9C0D7E08F44E@holtmann.org> <201412082015.18501@pali> <1418066813.1350.18.camel@dcbw.local> In-Reply-To: <1418066813.1350.18.camel@dcbw.local> Content-Type: text/plain; charset=utf-8; format=flowed Sender: linux-wireless-owner@vger.kernel.org List-ID: On 8.12.2014 21:26, Dan Williams wrote: > > a) change driver to prefer a new "wl1251-nvs-n900.bin" file, but fall > back to "wl1251-nvs.bin" if the first one isn't present > b) have a "wl1251-cal-nvs-update" service that, if wl1521-nvs-n900.bin > is *not* present mounts the CAL MTD, reads the data, writes it out into > wl1521-nvs-n900.bin, and the rmmod/modprobes the driver > > and done? Stuff that's not N900 just wouldn't ship the update service > and would proceed like none of this happened. > > Dan > > That would mean that the driver should not be built-in, as afaik we cannot rmmod built-in drivers. Sure, it will work after a reboot, but this is a bit hacky, agree? Also, new NVS file needs to be loaded when fcc regulation changes(flying abroad), so that would mean that the device would be outside of those until reboot (in case of built-in driver) Ivo