Re: e100: checksum mismatch on 82551ER rev10

2006-08-06 Thread Anton Blanchard
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

Re: e100: checksum mismatch on 82551ER rev10

2006-08-05 Thread Jason Lunz
[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 humb

Re: e100: checksum mismatch on 82551ER rev10

2006-08-05 Thread Molle Bestefich
David Miller wrote: Please put the option into the e100 driver to allow trying to use the device even if the EEPROM checksum is wrong. Whee, the users win! :-) If an Intel developer doesn't do it, I will. I hope you don't piss off the nice guys at Intel who contribute source code to the Lin

Re: e100: checksum mismatch on 82551ER rev10

2006-08-04 Thread David Miller
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 us

Re: e100: checksum mismatch on 82551ER rev10

2006-08-04 Thread David Miller
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 maintain

Re: e100: checksum mismatch on 82551ER rev10

2006-08-04 Thread Molle Bestefich
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 sent

Re: [bug] e100: checksum mismatch on 82551ER rev10

2006-08-02 Thread Auke Kok
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 sentence at all. You're s

Re: [bug] e100: checksum mismatch on 82551ER rev10

2006-08-02 Thread Charlie Brady
On Wed, 2 Aug 2006, Auke Kok wrote: [cc-ing netdev] [adding original thread authors back, please do not strip CC] [There were no Cc's visible in the lkml archive I used as source of my quotes.] Charlie Brady wrote: Let's assume that these things are all true, and the NIC currently does

Re: [bug] e100: checksum mismatch on 82551ER rev10

2006-08-02 Thread Auke Kok
[cc-ing netdev] [adding original thread authors back, please do not strip CC] Charlie Brady wrote: Molle Bestefich wrote: The NICs are working perfectly. How can you tell? Do you know if jumbo frames work correctly? Is the device properly checksumming? is flow control working properly? These a