On 6/30/2025 8:00 PM, Simon Horman wrote:
On Mon, Jun 30, 2025 at 10:35:00AM +0200, Jacek Kowalski wrote:
As described by Vitaly Lifshits:
Starting from Tiger Lake, LAN NVM is locked for writes by SW, so the
driver cannot perform checksum validation and correction. This means
that all NVM images must leave the factory with correct checksum and
checksum valid bit set.
Unfortunately some systems have left the factory with an uninitialized
value of 0xFFFF at register address 0x3F (checksum word location).
So on Tiger Lake platform we ignore the computed checksum when such
condition is encountered.
Signed-off-by: Jacek Kowalski <ja...@jacekk.info>
Tested-by: Vlad URSU <v...@ursu.me>
Fixes: 4051f68318ca9 ("e1000e: Do not take care about recovery NVM checksum")
Cc: sta...@vger.kernel.org
Thanks for the update.
Reviewed-by: Simon Horman <ho...@kernel.org>
Reviewed-by: Vitaly Lifshits <vitaly.lifsh...@intel.com>
