Hi,
On 16-03-15 11:16, Olliver Schinagl wrote:
Hey Hans,
<snip>
We will be using Lime2's which all have them, all lime's have them. Obviously
there will be a check, to check if there is a valid eeprom with valid data, but
for our product it will be required.
Since we will be flashing a generic image (all devices equal) and thus need to
have the 'uniqueness' of a device in the eeprom
I see, yes using olinuxino's embedded in factory devices is a valid reason,
so I will be happy to take patches for reading the MAC from the eeprom,
we will need to do some tests to make sure that we only do this on
valid eeproms though, I think it would be good to add a checksum +
all 00 test, or a crc check, note a checksum is fine by me, but if
there is ready to use crc code somewhere in u-boot that works for me too.
Yeah, absolutly. We probably want have a little very quick brainstorm as to how
and what we want to store. In our case, I think we probably want the eeprom it
its full form stored at the beginning of the eeprom, some checksum/crc,
followed by a few reserved bytes maybe. After that a serial number. My first
thought was to store the serial number in the eeprom and create a mac from
that, but now, that sounds like a bad idea. Optionally, it could be possible to
store the mac-prefix and serial number seperatly, and the LSB is used for the
second half of the mac? I don't know yet, just throwing up
some idea's.
The biggest problem right now is to get the 2nd and 3rd i2c adapters working,
as the current marvell driver only supports single I2C devices. But I hope to
send patches for that in a few weeks/couple of months.
Ok, note if you work on this please just convert the driver to the
driver model, rather then using the old multiple i2c adapter stuff.
Regards,
Hans
--
You received this message because you are subscribed to the Google Groups
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
