Andy H wrote:
Yes this should be more than enough for data!
I am happy with "high" or anything that is not "far".
I am more than happy to be way off base, but the libraries looks to
already be using _far:
When I ported some code recently from M644(p) to M1281, I had to fix this:
#if FLASHEND > 0xffff
for(i = 0;i < sizeof(bootldrinfo_t);i++) {
((uint8_t*)¤t_bootldrinfo)[i] = pgm_read_byte_far(FLASHEND -
BOOTLDRSIZE - sizeof(bootldrinfo_t) + 1 + i);
}
#else
memcpy_P(¤t_bootldrinfo, (uint8_t*) FLASHEND - BOOTLDRSIZE -
sizeof(bootldrinfo_t) + 1, sizeof(bootldrinfo_t));
#endif
If I'm correct, I think developers such as myself would expect the
functions to be _near and _far, with an alias of _near to the old
function name for larger devices like the 128/1280/1281/...
Of course, please ignore if I've misunderstood things.
Jim
_______________________________________________
AVR-GCC-list mailing list
AVR-GCC-list@nongnu.org
http://lists.nongnu.org/mailman/listinfo/avr-gcc-list
