Realtek network card driver, if_re.c:
CFG5 register writen after config register write done claimed. Yes, some documentation show that it's not necesarry to be in such mode to write CFG5, but it's unclear it apply to all chip versions.
See SVN rev 232145 comment also.
It's good to be consistent in all parts of code. All other writes to CFG5 register in module are done in "EEPROM write enable" mode but this one in re_clrwol() (see re_setwol and re_attach routines)
2. unecesarry writes into EEPROM (e.g. write of data althougth unchanged)
There are several places, where config register is read, examined, sometime) modified, then written back into EEPROM.
Unfortunately, they are written back unconditionally, whenever they has been modified or not.
As EEPROM have limited number of write cycles, such behavior may short lifetime of network card
Fix:  - move CFG5 write before "EEPROM write mode" close. It's better to be on safe side and it doesn't harm anything even it's not necesarry for particular chip
 - store original value of configuration register read, write back only if changed
How-To-Repeat: see description
Over to maintainer(s).
For bugs matching the following criteria:
Status: In Progress Changed: (is less than) 2014-06-01
Reset to default assignee and clear in-progress tags.
Mail being skipped