diff options
| author | Jacek Kowalski <[email protected]> | 2025-06-30 08:35:00 +0000 |
|---|---|---|
| committer | Tony Nguyen <[email protected]> | 2025-07-21 17:31:09 +0000 |
| commit | 61114910a5f6a71d0b6ea3b95082dfe031b19dfe (patch) | |
| tree | a462f80fe38940cf47fee03f3766f298de646340 /rust/helpers/task.c | |
| parent | e1000e: disregard NVM checksum on tgp when valid checksum bit is not set (diff) | |
| download | kernel-61114910a5f6a71d0b6ea3b95082dfe031b19dfe.tar.gz kernel-61114910a5f6a71d0b6ea3b95082dfe031b19dfe.zip | |
e1000e: ignore uninitialized checksum word on tgp
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]
Reviewed-by: Simon Horman <[email protected]>
Reviewed-by: Vitaly Lifshits <[email protected]>
Tested-by: Mor Bar-Gabay <[email protected]>
Signed-off-by: Tony Nguyen <[email protected]>
Diffstat (limited to 'rust/helpers/task.c')
0 files changed, 0 insertions, 0 deletions