[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240207103135.33e01d2d@kernel.org>
Date: Wed, 7 Feb 2024 10:31:35 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Elad Nachman <enachman@...vell.com>
Cc: Köry Maincent <kory.maincent@...tlin.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>, Taras Chornyi
<taras.chornyi@...ision.eu>, Thomas Petazzoni
<thomas.petazzoni@...tlin.com>, Miquel Raynal <miquel.raynal@...tlin.com>
Subject: Re: [EXT] Prestera driver fail to probe twice
On Wed, 7 Feb 2024 15:06:34 +0000 Elad Nachman wrote:
> MAGIC value is cleared after FW is downloaded to RAM, just before it is executed.
> So checking the MAGIC value to determine if the firmware is running is useless.
>
> You will get the MAGIC value read correctly only when firmware is
> during the download process, which does not help you implementing the
> logic you want.
I'm not aware of other networking drivers which cannot be reloaded /
rebound. I think it's part of base expectations for upstream drivers.
Could you work on fixing this?
IIRC we have enum devlink_param_reset_dev_on_drv_probe_value to control
whether device is always reset on driver load. You can make resetting
an opt-in if you're concerned about backward compatibility.
Powered by blists - more mailing lists