fix for bad macaddr of e1000 in Windows 2003 server with original MS driver
The sequence of reading from eeprom is "offset by one" moved because of a false detection of a clock cycle after an eeprom reset. Keeping the last clock value after a reset keeps it in sync. Signed-off-by: Naphtali Sprei <nsprei@redhat.com> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> Signed-off-by: Glauber Costa <glommer@redhat.com>
This commit is contained in:
committed by
Glauber Costa
parent
9eab386edb
commit
07fdfe83cf
@@ -262,6 +262,11 @@ set_eecd(E1000State *s, int index, uint32_t val)
|
||||
}
|
||||
if (!(val & E1000_EECD_CS)) { // rising, no CS (EEPROM reset)
|
||||
memset(&s->eecd_state, 0, sizeof s->eecd_state);
|
||||
/*
|
||||
* restore old_eecd's E1000_EECD_SK (known to be on)
|
||||
* to avoid false detection of a clock edge
|
||||
*/
|
||||
s->eecd_state.old_eecd = E1000_EECD_SK;
|
||||
return;
|
||||
}
|
||||
s->eecd_state.val_in <<= 1;
|
||||
|
Reference in New Issue
Block a user