<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Nov 4, 2013 at 2:05 PM, joem <span dir="ltr"><<a href="mailto:joem@martindale-electric.co.uk" target="_blank">joem@martindale-electric.co.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">: yes.  my concerns here are that the EEPROM would be overwritten by<br>

<div class="im">:user applications otherwise, potentially destroying the ability of CPU<br>
:Cards to identify the device.<br>
<br>
</div>I2C eeproms dirt cheap - have two eeproms - one user data (such as calibration data<br>
for instruments, keys, etc) and one for system data.<br>
<div class=""><div class="h5"><br>
_______________________________________________<br>
arm-netbook mailing list <a href="mailto:arm-netbook@lists.phcomp.co.uk">arm-netbook@lists.phcomp.co.uk</a><br>
<a href="http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook" target="_blank">http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook</a><br>
Send large attachments to <a href="mailto:arm-netbook@files.phcomp.co.uk">arm-netbook@files.phcomp.co.uk</a><br>
</div></div></blockquote></div><br>Given the need for device-tree info, and RID, etc etc, presumably, how large of an EEPROM would we technically need?<div><br></div><div>The Most recent revision MEBs have a 64K EEPROM, perhaps we could split the single eeprom memory into two segments? </div>
<div><br></div>-- <br><div dir="ltr"><div style="font-family:arial;font-size:small">Christopher Thomas</div><div style="font-family:arial;font-size:small">Firemoth Industries, LLC - Owner</div><div style="font-family:arial;font-size:small">
<a href="mailto:christopher@firemothindustries.com" target="_blank">christopher@firemothindustries.com</a></div><div style="font-family:arial;font-size:small"><span title="Call with Google Voice">214-458-5990</span></div>
</div>
</div></div>