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 <[email protected]> > Tested-by: Vlad URSU <[email protected]> > Fixes: 4051f68318ca9 ("e1000e: Do not take care about recovery NVM checksum") > Cc: [email protected]
Thanks for the update. Reviewed-by: Simon Horman <[email protected]>
