[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241218191346.5c974cb5@kernel.org>
Date: Wed, 18 Dec 2024 19:13:46 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Michael Chan <michael.chan@...adcom.com>
Cc: davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com,
pabeni@...hat.com, andrew+netdev@...n.ch, pavan.chebbi@...adcom.com,
andrew.gospodarek@...adcom.com, Ajit Khaparde <ajit.khaparde@...adcom.com>,
Kalesh AP <kalesh-anakkur.purayil@...adcom.com>, Somnath Kotur
<somnath.kotur@...adcom.com>
Subject: Re: [PATCH net-next v2 5/6] bnxt_en: Skip reading PXP registers
during ethtool -d if unsupported
On Tue, 17 Dec 2024 10:26:19 -0800 Michael Chan wrote:
> Newer firmware does not allow reading the PXP registers during
> ethtool -d, so skip the firmware call in that case. Userspace
> (bnxt.c) always expects the register block to be populated so
> zeroes will be returned instead.
We have both the ability to return the number of registers (regs_len),
and the regs->version. Are you sure you don't want to use either option
to let user space know the regs aren't there?
Powered by blists - more mailing lists