Re: [avr-libc-dev] [RFC] New eeprom.h

[Shaun Jackman]

Well, your suggestion would solve the code size issue, but the
function wouldn't be particularly fast if all the EEPROM register
accesses were indirectly addressed. In most applications, EEPROM
writes aren't usually time critical; although I can imagine that
exceptions exist.

Do the EEPROM registers always fall in the same locations from a
single base offset address?

Cheers,
Shaun

On Thu, Feb 28, 2008 at 11:48 AM, Rick Altherr <address@hidden> wrote:
>  Well, it would require one function per unique EEPROM register
>  location.  In fact, even that isn't true.  It requires one function
>  per unique code sequence required.  The register locations could be
>  arguments to the function that are supplied in the header's generic
>  macro.