[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-libc-dev] avr/iousbxx6_7.h: INT0_vect versus SIG_INTERRUPT0
From: |
Uwe Bonnes |
Subject: |
Re: [avr-libc-dev] avr/iousbxx6_7.h: INT0_vect versus SIG_INTERRUPT0 |
Date: |
Fri, 7 Sep 2012 15:28:09 +0200 |
>>>>> "Joerg" == Joerg Wunsch <address@hidden> writes:
Joerg> As Uwe Bonnes wrote:
>> Is this intentional?
Joerg> Yes, it is.
>> Or would a patch defining all those SIG_XXXY be accepted?
Joerg> By no means. ;-)
Joerg> The old term "signal" and the respective interrupt vector naming
Joerg> has been deprecated 7 years ago. The old SIG_* vector names are
Joerg> only kept for compatibility reasons in those header files where
Joerg> they did already exist by that time. All newer header files only
Joerg> get *_vect style names.
Joerg> Ethernut should finally catch up.
But avr-libc-1.8.0 is also inconstant:
./iocanxx.h-#define SPM_READY_vect _VECTOR(36)
./iocanxx.h:#define SIG_SPM_READY _VECTOR(36)
versus
./iom16a.h:#define SPM_RDY_vect_num 20
./iom16a.h:#define SPM_RDY_vect _VECTOR(20) /* Store Program Memory Ready
*/
or
./io4433.h:#define ANA_COMP_vect _VECTOR(13)
./io4433.h-#define SIG_COMPARATOR _VECTOR(13)
versus
./iocanxx.h:#define ANALOG_COMP_vect _VECTOR(24)
./iocanxx.h-#define SIG_COMPARATOR _VECTOR(24)
Should I provide a patch against avr-libc-1.8.0 or are the name differences
SIG_SPM_READY vs SPM_READY_vect and ANA_COMP_vect vs ANALOG_COMP_vect
intentional.
Anyway, ethernut now needs
/* avr-libc up to at least 1.8 is inconsistant about some _vect names */
#if !defined(SPM_READY_vect) && defined(SPM_RDY_vect)
#define SPM_READY_vect SPM_RDY_vect
#endif
as any patch will need a long time until it propagates to the users.
Bye
--
Uwe Bonnes address@hidden
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------