avr-libc-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Shaun Jackman
Subject: Re: [avr-libc-dev] [RFC] New eeprom.h
Date: Thu, 28 Feb 2008 10:23:44 -0800

The solution you're recommending is possible, and in fact probably the
only solution with the current architecture. The only catch is that it
requires one device-specific function for each location of the EEPROM
registers. How many EEPROM register locations are there across the AVR
product line?

Cheers,
Shaun

On Thu, Feb 28, 2008 at 9:53 AM, Rick Altherr <address@hidden> wrote:
>  While it's possibly a bit late for this option, you could write device-
>  specific methods with different function names.  Then, the header file
>  can defined a macro that expands the generic function name that gets
>  used in the source code to one of the specific methods.  That should
>  result in a larger library overall, but only the function used by the
>  device will actually be pulled into the final binary.  It would
>  prevent inlining any code at all.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]