[Arm-netbook] defining the eoma68 eeprom usage

[Aaron J. Seigo]

On Monday, November 4, 2013 21:47:51 Derek wrote:
> joem <joem <at> martindale-electric.co.uk> writes:
> > I2C eeproms dirt cheap - have two eeproms - one user data (such as
> 
> calibration data
> 
> > for instruments, keys, etc) and one for system data.
> 
> Note, you already need 2 eeproms, one on the CPU card and one on the carrier
> board.  I believe they are supposed to be on different I2C busses?

yes; i2c devices on the card are required to be on an internal-only i2c bus, 
for the obvious addressing collision problems that would arise otherwise.

> However, any time you're going to put user-data in a location, why not use
> mass-storage?

for the same reason we don’t put the device tree or device id in mass storage 
:)

-- 
Aaron J. Seigo