Re: [avr-libc-dev] Adding (some) Procyon AVRlibfunctionalitytoavr-libc

[Ruud Vlaming]

On Saturday 19 September 2009 17:41, Mike Perks wrote:

> I think one of the areas that is going to cause a lot of work is the 
> different definitions of I/O pins, ports and flags between different 
> processors. I wish Atmel would make things more consistent whenever they 
> come out with a new device. Things aren't even consistent within a 
> particular device family with the possible exception of xmegas. For my 
> projects I end up defining some common names and then #defining the 
> particular device configuration to those defines. It would be great if 
> we could do something this automagically from the XML files.

I don't think that is a good idea. The names are in most cases inconsistent
because there are also some small differences in the way the registers
are used or how they work, or how they work in conjunction with the
other peripherals. For a number of registers, it is possible to automatically 
define, in retrospect, abstract names which can address them in a generic
way, but certainly not for all. 

I would say, don't spend your energy there. The number of devices is 
not that great, and once they are done, there done. I don't think
you are going to beat the oldfashioned 'doing by hand' here.
I least i didn't for the devices my Femto OS supports (44 ports).
By hand you could define generic accessors which makes virtualized
use of the libs possible. Don't try to be complete from the beginning,
but let it grow, and dare to change it, without trying to be backward
compatible. Then you probably end up with something beautiful. 

Ruud.