[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [avr-libc-dev] [RFC] New eeprom.h
From: |
Weddington, Eric |
Subject: |
RE: [avr-libc-dev] [RFC] New eeprom.h |
Date: |
Wed, 30 Jan 2008 07:19:05 -0700 |
> -----Original Message-----
> From: Wouter van Gulik [mailto:address@hidden
> Sent: Wednesday, January 30, 2008 3:55 AM
> To: Weddington, Eric
> Cc: Joerg Wunsch; address@hidden
> Subject: Re: [avr-libc-dev] [RFC] New eeprom.h
>
> Weddington, Eric schreef:
>
> > - I need to fix a GCC bug, support *all* AVR device
> variants with the
> > EEPROM API, *and support future AVR devices that will be coming out
> > within a month*.
>
> If the gcc bug fix is the main reason,
No, the GCC bug fix is just one reason. Another reason is that the
EEPROM API doesn't work on 2 devices (IIRC). Another reason, is that the
EEPROM implementation needs to be flexible for new devices that are
coming out. All of these reasons have equal value. It just so happens
that we can address all three reasons just by reimplementing the header.
Re: [avr-libc-dev] [RFC] New eeprom.h, Preston Wilson, 2008/01/28
- RE: [avr-libc-dev] [RFC] New eeprom.h, Weddington, Eric, 2008/01/28
- Re: [avr-libc-dev] [RFC] New eeprom.h, Wouter van Gulik, 2008/01/29
- RE: [avr-libc-dev] [RFC] New eeprom.h, Weddington, Eric, 2008/01/29
- Re: [avr-libc-dev] [RFC] New eeprom.h, Joerg Wunsch, 2008/01/29
- RE: [avr-libc-dev] [RFC] New eeprom.h, Weddington, Eric, 2008/01/29
- Re: [avr-libc-dev] [RFC] New eeprom.h, Wouter van Gulik, 2008/01/30
- RE: [avr-libc-dev] [RFC] New eeprom.h,
Weddington, Eric <=
Re: [avr-libc-dev] [RFC] New eeprom.h, Wouter van Gulik, 2008/01/30