From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Lunn Subject: Re: [PATCH net-next] mlxsw: Make MLXSW_SP1_FWREV_MINOR a hard requirement Date: Mon, 24 Sep 2018 00:04:17 +0200 Message-ID: <20180923220417.GA31923@lunn.ch> References: <20180923144855.26444-1-idosch@mellanox.com> <20180923205809.GA30338@lunn.ch> <20180923215100.GA24149@splinter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Ido Schimmel , netdev@vger.kernel.org, davem@davemloft.net, jiri@mellanox.com, petrm@mellanox.com, mlxsw@mellanox.com To: Ido Schimmel Return-path: Received: from vps0.lunn.ch ([185.16.172.187]:42978 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725741AbeIXEDZ (ORCPT ); Mon, 24 Sep 2018 00:03:25 -0400 Content-Disposition: inline In-Reply-To: <20180923215100.GA24149@splinter> Sender: netdev-owner@vger.kernel.org List-ID: On Mon, Sep 24, 2018 at 12:51:00AM +0300, Ido Schimmel wrote: > On Sun, Sep 23, 2018 at 10:58:09PM +0200, Andrew Lunn wrote: > > > Therefore tweak the check to accept any FW version that is: > > > > > > - on the same branch as the preferred version, and > > > - the same as or newer than the preferred version. > > > > Hi Ido > > > > Do you print this information out? If the check fails, it would be > > useful to know what the minimal version is. > > Hi Andrew, > > Yes, we do print it. It is the version the driver will try to load > during initialization in case current version is incompatible: > > dev_info(mlxsw_sp->bus_info->dev, "Flashing firmware using file %s\n", > fw_filename); Ah. O.K. Thanks. But doesn't that mean you reflash the device with the minimum version, when in fact there could be a much newer version in /lib/firmware? Andrew