From: Joerg Wunsch <j@uriah.heep.sax.de>
To: binutils@sourceware.org
Subject: maintainer update: add support for more AVR microcontrollers
Date: Thu, 20 Apr 2006 01:52:00 -0000 [thread overview]
Message-ID: <20060419193241.GA77330@uriah.heep.sax.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 667 bytes --]
Hi again,
here's another small patch to add support for more Atmel AVR
microcontrollers. Atmel renamed some of their parts, and added
variants that need to be handled differently from their original
counterparts inside the library.
(My binutils copyright assignment is on file with the FSF.)
gas/ChangeLog:
* config/tc-avr.c (mcu_types): Add support for atmega165p,
atmega169p and atmega644p device. Rename atmega164/atmega324
devices to atmega164p/atmega324p.
--
cheers, J"org .-.-. --... ...-- -.. . DL8DTL
http://www.sax.de/~joerg/ NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)
[-- Attachment #2: binutils-ATmegaXXXP.diff --]
[-- Type: text/plain, Size: 1573 bytes --]
Index: src/gas/config/tc-avr.c
===================================================================
RCS file: /cvs/src/src/gas/config/tc-avr.c,v
retrieving revision 1.32
diff -u -r1.32 tc-avr.c
--- src/gas/config/tc-avr.c 7 Apr 2006 15:18:08 -0000 1.32
+++ src/gas/config/tc-avr.c 19 Apr 2006 15:13:26 -0000
@@ -116,13 +116,15 @@
{"atmega161", AVR_ISA_M161, bfd_mach_avr5},
{"atmega162", AVR_ISA_M323, bfd_mach_avr5},
{"atmega163", AVR_ISA_M161, bfd_mach_avr5},
- {"atmega164", AVR_ISA_M323, bfd_mach_avr5},
+ {"atmega164p",AVR_ISA_M323, bfd_mach_avr5},
{"atmega165", AVR_ISA_M323, bfd_mach_avr5},
+ {"atmega165p",AVR_ISA_M323, bfd_mach_avr5},
{"atmega168", AVR_ISA_M323, bfd_mach_avr5},
{"atmega169", AVR_ISA_M323, bfd_mach_avr5},
+ {"atmega169p",AVR_ISA_M323, bfd_mach_avr5},
{"atmega32", AVR_ISA_M323, bfd_mach_avr5},
{"atmega323", AVR_ISA_M323, bfd_mach_avr5},
- {"atmega324", AVR_ISA_M323, bfd_mach_avr5},
+ {"atmega324p",AVR_ISA_M323, bfd_mach_avr5},
{"atmega325", AVR_ISA_M323, bfd_mach_avr5},
{"atmega329", AVR_ISA_M323, bfd_mach_avr5},
{"atmega3250",AVR_ISA_M323, bfd_mach_avr5},
@@ -131,6 +133,7 @@
{"atmega64", AVR_ISA_M323, bfd_mach_avr5},
{"atmega640", AVR_ISA_M323, bfd_mach_avr5},
{"atmega644", AVR_ISA_M323, bfd_mach_avr5},
+ {"atmega644p",AVR_ISA_M323, bfd_mach_avr5},
{"atmega128", AVR_ISA_M128, bfd_mach_avr5},
{"atmega1280",AVR_ISA_M128, bfd_mach_avr5},
{"atmega1281",AVR_ISA_M128, bfd_mach_avr5},
next reply other threads:[~2006-04-19 19:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 1:52 Joerg Wunsch [this message]
2006-04-20 10:51 ` Jan-Benedict Glaw
2006-04-20 10:53 ` Eric Christopher
2006-04-20 11:05 ` Joerg Wunsch
2006-04-20 14:24 ` Eric Christopher
2006-04-21 6:55 ` Joerg Wunsch
2006-04-22 14:20 Björn Haase
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060419193241.GA77330@uriah.heep.sax.de \
--to=j@uriah.heep.sax.de \
--cc=binutils@sourceware.org \
--cc=joerg_wunsch@uriah.heep.sax.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).