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
[EMAIL PROTECTED] said:
And BTW I want to remind the entire world that the last time Intel
cried wolf to all of us about vendors using broken EEPROMs with their
networking chips it turned out to be a bug in one of the patches Intel
put into the Linux driver. :-)
Intel should really humble
Auke Kok wrote:
Charlie Brady wrote:
Let's assume that these things are all true, and the NIC currently does
not work perfectly, just imperfectly, but acceptably. With the recent
driver change, it now does not work at all. That's surely a bug in the
driver.
There is no logic in that
From: Molle Bestefich [EMAIL PROTECTED]
Date: Fri, 4 Aug 2006 13:04:07 +0200
You're trying to pull Linux end users into a war between Intel and
it's vendors, so you can make end users scream at the vendors when
they forget to run the checksum tool.
I totally agree, Intel driver maintainers
From: David Miller [EMAIL PROTECTED]
Date: Fri, 04 Aug 2006 04:20:24 -0700 (PDT)
I totally agree, Intel driver maintainers generally act like complete
idiots in these kinds of situations.
If the EEPROM has a broken checksum, the user should have an option
that allows him to try and use the
