From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19440 invoked by alias); 20 Apr 2006 05:08:51 -0000 Received: (qmail 19430 invoked by uid 22791); 20 Apr 2006 05:08:50 -0000 X-Spam-Check-By: sourceware.org Received: from uriah.heep.sax.de (HELO uriah.heep.sax.de) (213.240.137.9) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 20 Apr 2006 05:08:47 +0000 Received: from localhost (localhost [127.0.0.1]) by uriah.heep.sax.de (Postfix) with ESMTP id 4BE9A196; Thu, 20 Apr 2006 07:08:41 +0200 (MET DST) Received: from uriah.heep.sax.de (localhost [127.0.0.1]) by localhost (AvMailGate-2.0.2-10) id 21267-7687A96B; Thu, 20 Apr 2006 07:08:41 +0200 Received: from uriah.heep.sax.de (localhost [127.0.0.1]) by uriah.heep.sax.de (Postfix) with ESMTP id 9A34750; Thu, 20 Apr 2006 07:08:35 +0200 (MET DST) Received: from uriah.heep.sax.de (localhost [127.0.0.1]) by uriah.heep.sax.de (Postfix) with ESMTP; Thu, 20 Apr 2006 07:08:35 +0200 (MET DST) Received: (from j@localhost) by uriah.heep.sax.de (8.13.4/8.13.1/Submit) id k3K58YR0021266; Thu, 20 Apr 2006 07:08:34 +0200 (MET DST) (envelope-from j) Date: Thu, 20 Apr 2006 11:05:00 -0000 From: Joerg Wunsch To: Eric Christopher Cc: Jan-Benedict Glaw , binutils@sourceware.org Subject: Re: maintainer update: add support for more AVR microcontrollers Message-ID: <20060420050834.GC73791@uriah.heep.sax.de> Reply-To: Joerg Wunsch References: <20060419193241.GA77330@uriah.heep.sax.de> <20060420014708.GM13324@lug-owl.de> <234616A5-B9B9-4A30-867D-3CD053064067@apple.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="k1lZvvs/B4yU6o8G" Content-Disposition: inline In-Reply-To: <234616A5-B9B9-4A30-867D-3CD053064067@apple.com> X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-GPG-Fingerprint: 5E84 F980 C3CA FD4B B584 1070 F48C A81B 69A8 5873 User-Agent: Mutt/1.5.11 X-AntiVirus: checked by AntiVir MailGate (version: 2.0.2-10; AVE: 6.33.0.19; VDF: 6.33.0.62; host: uriah.heep.sax.de) Mailing-List: contact binutils-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sourceware.org X-SW-Source: 2006-04/txt/msg00275.txt.bz2 --k1lZvvs/B4yU6o8G Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 2354 As Eric Christopher wrote: > >>- {"atmega164", AVR_ISA_M323, bfd_mach_avr5}, > >>+ {"atmega164p",AVR_ISA_M323, bfd_mach_avr5}, > > > >>- {"atmega324", AVR_ISA_M323, bfd_mach_avr5}, > >>+ {"atmega324p",AVR_ISA_M323, bfd_mach_avr5}, > > > >I'm not an AVR user, but from a user's perspective, this is an > >interface change and should be documented. > Agreed, I think that unless there's a reason you should keep both. There is a reason: the ATmega164 and ATmega324 never really existed in silicon, and Atmel literally renamed these devices before releasing the first silicon for them. Things are different for the ATmega644 which does exist in its original form, so there we do have both devices now (and of course, we kept the old one). Yes, this is really weird, I know. They originally announced ATmega164/324/644 to be one family, but funnily enough, the 164 and 324 had a wider feature set than the 644. ATmega644 engineering samples became available, but nothing except the datasheet for the smaller siblings (not even their device XML files which they are using for their own simulator). Now that they started their `picopower' program (which is indicated by the `P' suffix), they renamed the ATmega164/324 to 164P/324P (with their originally intented feature set), and complemented that one by an ATmega644P which has the same feature set as its smaller siblings, so there are now 644 and 644P with different feature sets. :-( I'm all but happy about that change (as it is the first time where a suffix letter really makes a difference for the device), but for whatever reason, that's their marketing decision. Likewise for the ATmega165/169 where both, the old and the 165P/169P versions do exist. They have the same feature set but some register naming has been changed, so we also have both devices in the list now. Documentation for the entire toolchain is mainly maintained as part of the avr-libc project: http://www.nongnu.org/avr-libc/user-manual/index.html Once a new library release is done that supports these new devices (most likely today or tomorrow), you'll be able to see their names in that list. --=20 cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) --k1lZvvs/B4yU6o8G Content-Type: application/pgp-signature Content-Disposition: inline Content-length: 189 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFERxdR9IyoG2moWHMRAhlmAKDa2PAQ7tqy9pldA7J1yIVCbHwqDQCghZf/ dTuu9MinX7n5NgZH9aBbMsk= =v+wT -----END PGP SIGNATURE----- --k1lZvvs/B4yU6o8G--