Hello,
these are a few patches that cumulated here related to the i210 network
controller.
These are nearly good enough to populate the attached flash with a valid
firmware (which you still need to have yourself) on all machines I have
access to.
There is still one (to me) known problem: When the flash doesn't contain
a valid image, accessing the eeprom (which is a simulated device on i210
that is backed up by shadow RAM and the two first pages of flash) gives
the contents of iNVM instead of the expected default eeprom. That
results in a few wrong turns in the code but they are not grave enough
to stop being able to write a valid firmware image.
A bit that is still missing is that a customer machine uses an flash
that is write protected at power on. An i210 with an programmed flash is
clever enough to remove the write protection before writing to it, but
that doesn't help when the flash is not programmed (tin opener inside).
I have a prototype that can remove the write protection with a
cryptic command but that's not ready for prime time yet.
Best regards
Uwe
Uwe Kleine-König (6):
net/e1000: fix coding style at a few locations
net/e1000: don't use the eeprom word size as timeout to get a
semaphore
net/e1000: reorder functions
net/e1000: provide access to iNVM even if a flash is present
net/e1000: fix size of invm device
net/e1000: provide device for accessing emulated eeprom
drivers/net/e1000/e1000.h | 8 +-
drivers/net/e1000/eeprom.c | 324 ++++++++++++++++++++++++++-------------------
drivers/net/e1000/main.c | 6 +-
3 files changed, 196 insertions(+), 142 deletions(-)
--
2.11.0
_______________________________________________
barebox mailing list
barebox@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/barebox
