[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-gcc-list] read write eeprom WINAVR20050214
|
From: |
Joerg Wunsch |
|
Subject: |
Re: [avr-gcc-list] read write eeprom WINAVR20050214 |
|
Date: |
Sat, 19 Feb 2005 08:02:30 +0100 (MET) |
"Royce & Sharal Pereira" <address@hidden> wrote:
> GCC has no idea of different address spaces. So your '&' option will
> not work here.
Well, the & operator would work anyway (it's just the developer's
responsibility to use the correct access function which he did), but
the typecast to (unsigned) makes it an incompatible type. As the
EEPROM functions take a pointer, but the cast makes an integer
type out of the pointer just obtained with &, that's nonsense.
--
cheers, J"org .-.-. --... ...-- -.. . DL8DTL
http://www.sax.de/~joerg/ NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)
- Re: [avr-gcc-list] read write eeprom WINAVR20050214, (continued)
- Re: [avr-gcc-list] read write eeprom WINAVR20050214, Royce & Sharal Pereira, 2005/02/17
- Re: [avr-gcc-list] read write eeprom WINAVR20050214, Julius Luukko, 2005/02/18
- Re: [avr-gcc-list] read write eeprom WINAVR20050214, Royce & Sharal Pereira, 2005/02/18
- RE: [avr-gcc-list] read write eeprom WINAVR20050214, Eivind Sivertsen, 2005/02/18
- Re: [avr-gcc-list] read write eeprom WINAVR20050214, E. Weddington, 2005/02/18
- Re: [avr-gcc-list] read write eeprom WINAVR20050214, andi, 2005/02/18
- Re: [avr-gcc-list] read write eeprom WINAVR20050214, Royce & Sharal Pereira, 2005/02/18
- Re: [avr-gcc-list] read write eeprom WINAVR20050214,
Joerg Wunsch <=
Re: [avr-gcc-list] read write eeprom WINAVR20050214, Dave Hansen, 2005/02/18
Re: [avr-gcc-list] read write eeprom WINAVR20050214, Paul Colin Gloster, 2005/02/22