lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-Id: <20190201.153638.647120007389173035.davem@davemloft.net> Date: Fri, 01 Feb 2019 15:36:38 -0800 (PST) From: David Miller <davem@...emloft.net> To: jakub.kicinski@...ronome.com Cc: netdev@...r.kernel.org, oss-drivers@...ronome.com, jiri@...nulli.us, andrew@...n.ch, f.fainelli@...il.com, mkubecek@...e.cz, eugenem@...com, jonathan.lemon@...il.com Subject: Re: [PATCH net-next v4 0/8] devlink: add device (driver) information API From: Jakub Kicinski <jakub.kicinski@...ronome.com> Date: Thu, 31 Jan 2019 10:50:39 -0800 > fw_version field in ethtool -i does not suit modern needs with 31 > characters being quite limiting on more complex systems. There is > also no distinction between the running and flashed versions of > the firmware. > > Since the driver information pertains to the entire device, rather > than a particular netdev, it seems wise to move it do devlink, at > the same time fixing the aforementioned issues. > > The new API allows exposing the device serial number and versions > of the components of the card - both hardware, firmware (running > and flashed). Driver authors can choose descriptive identifiers > for the version fields. A few version identifiers which seemed > relevant for most devices have been added to the global devlink > header. > > Example: ... > Last patch also includes a compat code for ethtool. If driver > reports no fw_version via the traditional ethtool API, ethtool > can call into devlink and try to cram as many versions as possible > into the 31 characters. ... Series applied.
Powered by blists - more mailing lists