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

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

RE: [avr-libc-dev] [bug #21410] Incorrect use of 16-bit eeprom addresses


From: Eric Weddington
Subject: RE: [avr-libc-dev] [bug #21410] Incorrect use of 16-bit eeprom addresses in devices with 8-Bit address registers
Date: Wed, 24 Oct 2007 09:19:46 -0600

 

> -----Original Message-----
> From: 
> address@hidden 
> [mailto:address@hidden
> org] On Behalf Of Joerg Wunsch
> Sent: Wednesday, October 24, 2007 4:56 AM
> To: Wouter; Robert von Knobloch; Joerg Wunsch; address@hidden
> Subject: [avr-libc-dev] [bug #21410] Incorrect use of 16-bit 
> eeprom addresses in devices with 8-Bit address registers
> 
> 
> Follow-up Comment #2, bug #21410 (project avr-libc):
> 
> > If we skip this then we might be ok, if the eeprom.S
> > file is build per device not per architecture.
> 
> Unfortunately, it actually *is* per architecture, not per
> device.  That's the reason why it is compiled into two
> different object files (for two different EEPROM base
> addresses).
> 
> The only way I'm seeing is to compile it into four different
> object files (base address vs. 8- or 16-bit addressing), and
> extend the macro wrapper logic in <avr/eeprom.h>.

Ugh. Please, let's not. I'd like to also consider future devices as well.
;-)

This is a strong argument for starting the work to lib-per-device, which
we're planning on doing anyway.

Or, as an alternative, turning the implementation of the EEPROM API into
inline-assembly macros so we can put off the lib-per-device task.

Eric
 





reply via email to

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