simulavr-devel
[Top][All Lists]
Advanced

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

RE: [Simulavr-devel] [patch #7032] unitialized HWUart, did neverfinish s


From: Weddington, Eric
Subject: RE: [Simulavr-devel] [patch #7032] unitialized HWUart, did neverfinish sending
Date: Tue, 22 Dec 2009 12:25:05 -0700

 

> -----Original Message-----
> From: 
> address@hidden 
> [mailto:address@hidden
> u.org] On Behalf Of Joerg Wunsch
> Sent: Monday, December 21, 2009 10:20 PM
> To: address@hidden
> Subject: Re: [Simulavr-devel] [patch #7032] unitialized 
> HWUart, did neverfinish sending
> 
> As Petr Hluzín wrote:
> 
> > Because the ATmegaXX is the canonical (manufacturer's) name. The
> > processor's name is ATmega16, not atmega16.  A compiler, simulator,
> > etc are not in position to reject official names.
> 
> OTOH, the lowercase form has been in use in the AVR-GCC toolchain all
> the time, and the compiler only accepts it as lowercase.  But of
> course, I wouldn't mind if other tools accepted it in any case.
> 
> > By the way avrdude uses (and used to require) a "code" of m16 for
> > that chip. What about requiring "m16"?
> 
> AVRDUDE only offers that as a shortcut alias.  It accepts the long
> name as well, and it is case independant when accepting the name.

And honestly, I would rather that avrdude got rid of those shortcut aliases, as 
it just confuses the end user. I would rather that it accepts the full 
lowercase name like avr-gcc, and possibly the full canonical (mixed case) name. 
It's not like these device names are incredibly long that they need to be 
abbreviated.




reply via email to

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