Re: [avr-libc-dev] Re: [bug #25300] Additional i/o port names

2009-04-12 Thread Frédéric Nadeau
On Sun, Apr 12, 2009 at 10:51 AM, Weddington, Eric eric.wedding...@atmel.com wrote: I'm open to ideas on a naming scheme. I'm working on the duplicate thing and I'm facing a critical issue. It has been decided that we should not care mutch if pins where active low or active high(such as

Re: [avr-libc-dev] Re: [bug #25300] Additional i/o port names

2009-04-12 Thread Bob Paddock
*sigh* I really wish the XML files were more consistent. Many of us have that wish too. In my view all of the individual XML files had to be unified in to a single large XML file, and standardized in the process of the conversion. Then an additional file merged in to add the information

[avr-libc-dev] [patch #6805] Numeric interrupt vectors

2009-04-12 Thread Anatoly Sokolov
Follow-up Comment #1, patch #6805 (project avr-libc): The patch for the GCC is not complete. 1. No numeric argument to the 'interrupt' attribute is implemented. 2. Not possible use one interrupt handler for some interrupt vectors. I propose to implement the interface for interrupt handler

RE: [avr-libc-dev] Re: [bug #25300] Additional i/o port names

2009-04-12 Thread Weddington, Eric
-Original Message- From: avr-libc-dev-bounces+eric.weddington=atmel@nongnu.org [mailto:avr-libc-dev-bounces+eric.weddington=atmel@nongnu. org] On Behalf Of Frédéric Nadeau Sent: Friday, April 10, 2009 1:31 PM To: avr-libc-dev@nongnu.org Subject: Re: [avr-libc-dev] Re:

RE: [avr-libc-dev] Re: [bug #25300] Additional i/o port names

2009-04-12 Thread Weddington, Eric
-Original Message- From: avr-libc-dev-bounces+eric.weddington=atmel@nongnu.org [mailto:avr-libc-dev-bounces+eric.weddington=atmel@nongnu. org] On Behalf Of Frédéric Nadeau Sent: Sunday, April 12, 2009 9:12 AM To: avr-libc-dev@nongnu.org Subject: Re: [avr-libc-dev] Re:

[avr-libc-dev] [patch #6805] Numeric interrupt vectors

2009-04-12 Thread Ron Kreymborg
Follow-up Comment #2, patch #6805 (project avr-libc): Good idea - a more complete implementation that mine (which was based on Marek's original). I assume it will use the number for the vector and not the handler_name (the C++ requirement). Just curious - what is an example of (2)? Ron