Re: [Bug #11382] e1000e: 2.6.27-rc1 corrupts EEPROM/NVM

[Krzysztof Halasa]

Jiri Kosina <jkosina@xxxxxxx> writes:

> Still, what confuses me a little bit -- the EEPROM of the card is set to 
> all 0xff, once the corruption happens. Isn't that a quite a coincidence, 
> that bytes representing "nothing" in this context are used?

Perhaps the entire chip has been erased with the "ERAL" (erase all)
command. Requires previously issued EWEN (erase/write enable).
Each command seems to require several writes to the EEPROM control
register.
-- 
Krzysztof Halasa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/