linux-kernel - Re: e100: checksum mismatch on 82551ER rev10

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

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20060806200809.GC4209@krispykreme>
Date:	Mon, 7 Aug 2006 06:08:09 +1000
From:	Anton Blanchard <anton@...ba.org>
To:	David Miller <davem@...emloft.net>
Cc:	molle.bestefich@...il.com, auke-jan.h.kok@...el.com,
	charlieb@...ge.apana.org.au, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: e100: checksum mismatch on 82551ER rev10


Hi,

> If the EEPROM has a broken checksum, the user should have an option
> that allows him to try and use the device anyways, end of story.

Ive come across this problem a number of times on e1000 chips (to be
clear it was vendor programming issues).

The driver has the option to read and write the EEPROM already. All we
need is the ability for the driver to hang around so that we can use
ethtool to fix it.

At the moment we carry an out of tree patch to do this.

Anton
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/