[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <MN2PR18MB3182AB7FB24C2F4EC9E16B64A10C0@MN2PR18MB3182.namprd18.prod.outlook.com>
Date: Wed, 22 Jan 2020 16:02:06 +0000
From: Michal Kalderon <mkalderon@...vell.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: Ariel Elior <aelior@...vell.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>
Subject: RE: [PATCH net-next 01/14] qed: FW 8.42.2.0 Internal ram offsets
modifications
> From: linux-rdma-owner@...r.kernel.org <linux-rdma-
> owner@...r.kernel.org> On Behalf Of Jakub Kicinski
>
> On Wed, 22 Jan 2020 17:26:14 +0200, Michal Kalderon wrote:
> > IRO stands for internal RAM offsets. Updating the FW binary produces
> > different iro offsets. This file contains the different values, and a
> > new representation of the values.
> >
> > Signed-off-by: Ariel Elior <ariel.elior@...vell.com>
> > Signed-off-by: Michal Kalderon <michal.kalderon@...vell.com>
>
> If you have different offsets depending on FW build - where is the code that
> checks the FW version is the one driver expects? At a quick glance you're not
> bumping any numbers in this patch..
The FW version is bumped in patch 0009-qed-FW-8.42.2.0-HSI-Changes.patch and the driver loads
The FW binary according to this version.
Powered by blists - more mailing lists