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
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 28 May 2019 10:55:31 +0200
From:   Jiri Pirko <>
To:     Florian Fainelli <>
Subject: Re: [patch net-next 0/7] expose flash update status to user

Mon, May 27, 2019 at 08:14:32PM CEST, wrote:
>On 5/23/2019 2:45 AM, Jiri Pirko wrote:
>> From: Jiri Pirko <>
>> When user is flashing device using devlink, he currenly does not see any
>> information about what is going on, percentages, etc.
>> Drivers, for example mlxsw and mlx5, have notion about the progress
>> and what is happening. This patchset exposes this progress
>> information to userspace.
>> See this console recording which shows flashing FW on a Mellanox
>> Spectrum device:
>It would be great to explain why you went that route instead of
>implementing a MTD device (like what sfc) which would have presumably
>allowed you to more or less the same thing using a standard device
>driver model that is establish with flash devices.

This patch is not adding flash functionality. It only adds the
visibility into already implemented flash process.

Also, re MTD, let me refer you to the discussion 2 years ago:
Subject: Re: [patch net-next 0/9] mlxsw: Support firmware flash
From: Yotam Gigi <>
Message-ID: <>
Date: Sun, 28 May 2017 10:26:49 +0300

Powered by blists - more mailing lists