avr-libc-dev
[Top][All Lists]
Advanced

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

Re: [avr-libc-dev] USART_RXC_vect and USART_TXC_vect


From: Karl Edler
Subject: Re: [avr-libc-dev] USART_RXC_vect and USART_TXC_vect
Date: Thu, 13 May 2010 11:45:25 -0500
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100228 SUSE/3.0.3-1.1.1 Thunderbird/3.0.3

Good policy. Thanks.

On 05/13/2010 11:02 AM, address@hidden wrote:
> Send AVR-libc-dev mailing list submissions to
>       address@hidden
>
> To subscribe or unsubscribe via the World Wide Web, visit
>       http://lists.nongnu.org/mailman/listinfo/avr-libc-dev
> or, via email, send a message with subject or body 'help' to
>       address@hidden
>
> You can reach the person managing the list at
>       address@hidden
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of AVR-libc-dev digest..."
>
>
> Today's Topics:
>
>    1. USART_RXC_vect and USART_TXC_vect (Karl Edler)
>    2. Re: USART_RXC_vect and USART_TXC_vect (Joerg Wunsch)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 12 May 2010 12:20:35 -0500
> From: Karl Edler <address@hidden>
> Subject: [avr-libc-dev] USART_RXC_vect and USART_TXC_vect
> To: address@hidden
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi,
>
> I have noticed that iom16.h, iom323.h, iom32.h, and iom8.h all define
> USART_RXC_vect and USART_TXC_vect
> while the headers for other micro-controllers define
> USART_RX_vect and USART_TX_vect instead.
>
> I think that these definitions should be unified. Am I right?
>
> If so, how might I unify them and have the changes contributed to the
> project?
>
> Cheers,
> Karl Edler
>
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 12 May 2010 20:20:28 +0200
> From: Joerg Wunsch <address@hidden>
> Subject: Re: [avr-libc-dev] USART_RXC_vect and USART_TXC_vect
> To: address@hidden
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=us-ascii
>
> As Karl Edler wrote:
>
>   
>> I think that these definitions should be unified. Am I right?
>>     
> Our policy is to match whatever the datasheet uses.  As the datasheet
> of the ATmega16 & Co. used USART,TXC, we have it that way, too.
>
> I don't think anyone is going to modify these very old datasheets
> anymore.
>   




reply via email to

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