From: "S, Pitchumani" <Pitchumani.S@atmel.com>
To: Denis Chertykov <chertykov@gmail.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Georg-Johann Lay <avr@gjlay.de>
Subject: RE: [Patch, avr] Add atmel ata5782 and ata5831 devices
Date: Mon, 14 Jul 2014 11:49:00 -0000 [thread overview]
Message-ID: <CAC140656783604CABA6AE60C2A6D5A497921E48@penmbx01> (raw)
In-Reply-To: <CADOs=zYP5X78YEfcQhRDwgqq_gPuPZo5aPfv8Xvyixa_T02b6w@mail.gmail.com>
> -----Original Message-----
> From: gcc-patches-owner@gcc.gnu.org [mailto:gcc-patches-owner@gcc.gnu.org]
> On Behalf Of Denis Chertykov
> Sent: Friday, July 11, 2014 9:53 PM
> To: S, Pitchumani
> Cc: gcc-patches@gcc.gnu.org; Georg-Johann Lay
> Subject: Re: [Patch, avr] Add atmel ata5782 and ata5831 devices
>
> 2014-07-11 12:50 GMT+04:00 S, Pitchumani <Pitchumani.S@atmel.com>:
> > This patch adds supports for Atmel's ata5782 and ata5831 devices.
> >
> > These devices ISA matches with AVR5 architecture except that text
> section
> > start for these two devices is 0x8000. By default 0x0 is used as the
> text
> > start address. This patch adds a device attribute for text start and
> that
> > is passed to Linker via -Ttext option.
> >
> > If OK, could someone commit please?
> >
> > Regards,
> > Pitchumani
> >
> > 2014-07-11 Pitchumani Sivanupandi <pitchumani.s@atmel.com>
> >
> > * config/avr/avr-arch.h (avr_mcu_t): Add text section start
> attribute.
> > * config/avr/avr-devices.c (AVR_MCU): Same.
> > (avr_mcu_types): add text start value to end of device list.
> > * config/avr/avr-mcus.def: Add text section start for all devices.
> > (ata5782): Add new avr5 device.
> > (ata5831): Same.
> > * config/avr/avr-tables.opt: Regenerate.
> > * config/avr/avr.h: Add declaration for text section start handler.
> > (EXTRA_SPEC_FUNCTIONS): Add text section start handler to SPEC
> functions.
> > (LINK_SPEC): Include text section start handler to linker spec.
> > * config/avr/driver-avr.c (avr_device_to_text_start): New function
> to
> > pass -Ttext option to linker if the text section start for the
> device is
> > not zero.
> > * config/avr/t-multilib: Regenerate.
> > * doc/avr-mmcu.texi: Regenerate.
> >
>
> Committed.
Hi Denis,
Thanks.
It seems you missed to include gcc/doc/avr-mmcu.texi file changes.
Regards,
Pitchumani
next prev parent reply other threads:[~2014-07-14 11:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 8:51 S, Pitchumani
2014-07-11 16:22 ` Denis Chertykov
2014-07-14 11:49 ` S, Pitchumani [this message]
2014-07-16 17:04 ` Denis Chertykov
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=CAC140656783604CABA6AE60C2A6D5A497921E48@penmbx01 \
--to=pitchumani.s@atmel.com \
--cc=avr@gjlay.de \
--cc=chertykov@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
/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).