[Top][All Lists]

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

[avr-libc-dev] [bug #38765] avr/iotnx5.h defines USI_OFL_vect not USI_OV

From: Joerg Wunsch
Subject: [avr-libc-dev] [bug #38765] avr/iotnx5.h defines USI_OFL_vect not USI_OVERFLOW_vect
Date: Thu, 18 Apr 2013 05:56:24 +0000
User-agent: Mozilla/5.0 (X11; FreeBSD i386; rv:19.0) Gecko/20100101 Firefox/19.0

Update of bug #38765 (project avr-libc):

                  Status:                    None => Wont Fix               
             Assigned to:                    None => joerg_wunsch           
             Open/Closed:                    Open => Closed                 


Follow-up Comment #1:

Our policy is to make the interrupt vector names match the
Atmel XML file, and the datasheet (to whatever is possible
in terms of a valid C name, e.g. by replacing spaces by

Since the datasheets and XML files of the various USI-equipped
AVRs don't agree on each other, our vector names don't either.
We did invent our own (self-consistent wrt. avr-libc) vector
names in the past, but this idea eventually turned out to be
unmaintainable, so as a matter of policy, we switched to
automatically generating them from the XML files.

The following devices appear to use OSI_OVF:

ATtiny87/167, ATtiny*4(A), ATtiny*5, ATtiny26, ATtiny*61(A),

The following devices appear to use OSI_OVERFLOW:

ATtiny2313(A), ATtiny4313, ATmega{16,32,64}{5,9}{,0}(PA)


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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