Re: [Arm-netbook] defining the eoma68 eeprom usage

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?

However, any time you're going to put user-data in a location, why not use mass-storage? Why put encryption keys into EEPROM? Either they should be bound to the device (use a ROM seperate from EOMA68 device-tree) or they should be mobile (store on HDD/SSD)