[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240405110058.GA5383@nvidia.com>
Date: Fri, 5 Apr 2024 08:00:58 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: Edward Cree <ecree.xilinx@...il.com>
Cc: Andrew Lunn <andrew@...n.ch>, David Ahern <dsahern@...nel.org>,
Jakub Kicinski <kuba@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Christoph Hellwig <hch@...radead.org>,
Saeed Mahameed <saeed@...nel.org>, Arnd Bergmann <arnd@...db.de>,
Leon Romanovsky <leonro@...dia.com>, Jiri Pirko <jiri@...dia.com>,
Leonid Bloch <lbloch@...dia.com>, Itay Avraham <itayavr@...dia.com>,
Saeed Mahameed <saeedm@...dia.com>,
Aron Silverton <aron.silverton@...cle.com>,
linux-kernel@...r.kernel.org,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Andy Gospodarek <andrew.gospodarek@...adcom.com>
Subject: Re: [PATCH V4 0/5] mlx5 ConnectX control misc driver
On Thu, Apr 04, 2024 at 09:53:14PM +0100, Edward Cree wrote:
> On 04/04/2024 21:25, Jason Gunthorpe wrote:
> > For instance there is a bunch that configure the UEFI option
> > rom. Various devices can PXE boot, iSCSI boot and so on.
>
> Sounds like a perfect example of something that should have a
> standardised cross-vendor configuration mechanism, rather than
> every vendor having its own special tool as is sadly the case
> today.
Sure, I imagine exploring this kind of commonality in userspace with a
fwctl based tool. The kernel is the wrong layer to do it.
Jason
Powered by blists - more mailing lists