From: "Kei Sakamoto" <sakamoto.kei@renesas.com>
To: <gdb-patches@sources.redhat.com>
Subject: Re: [patch] New m32r remote target, m32rsdi
Date: Thu, 16 Oct 2003 02:43:00 -0000 [thread overview]
Message-ID: <00ed01c3938f$50914550$5169910a@KEI> (raw)
In-Reply-To: <032401c39228$378ab450$5169910a@KEI>
I commited the following patch. Thanks.
Kei Sakamoto
Renesas Technology Corp.
From: "Kei Sakamoto" <sakamoto.kei@renesas.com>
To: "Andrew Cagney" <ac131313@redhat.com>
Cc: <gdb-patches@sources.redhat.com>
Sent: Tuesday, October 14, 2003 4:53 PM
Subject: Re: [patch] New m32r remote target, m32rsdi
> > Can you post what you've got, without worrying about the ASYNC part.
> >
> > Andrew
>
> I attached the revised patch. It is different from the last one as the
> following:
>
> - use serial.[ch] functions instead of socket library
> - documented (doc/gdb.texinfo)
> - add an entry in NEWS
>
> Kei
>
> ===
>
> ChangeLog:
>
> 2003-10-14 Kei Sakamoto <sakamoto.kei@renesas.com>
>
> * remote-m32r-sdi.c : New file, interface to m32r on-chip
> debug interface, SDI (Scalable Debug Interface).
> * NEWS: Mention m32r SDI protocol was supported.
> * Makefile.in (remote-m32r-sdi.o): Add build rule.
> * config/m32r/m32r.mt (TDEPFILES) : Add remote-m32r-sdi.o.
>
> doc/ChangeLog:
>
> 2003-10-14 Kei Sakamoto <sakamoto.kei@renesas.com>
>
> * gdb.texinfo (M32R/D): Mention m32rsdi target.
>
prev parent reply other threads:[~2003-10-16 2:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 7:57 Kei Sakamoto
2003-08-17 21:03 ` Daniel Jacobowitz
2003-08-21 4:29 ` Kei Sakamoto
2003-09-05 2:59 ` Kei Sakamoto
2003-09-05 14:21 ` Andrew Cagney
2003-09-08 6:13 ` Kei Sakamoto
2003-09-22 7:14 ` Andrew Cagney
2003-10-02 2:26 ` Kei Sakamoto
2003-10-10 1:41 ` Andrew Cagney
2003-10-14 7:53 ` Kei Sakamoto
2003-10-15 5:51 ` Eli Zaretskii
2003-10-15 14:40 ` Andrew Cagney
2003-10-16 2:43 ` Kei Sakamoto [this message]
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='00ed01c3938f$50914550$5169910a@KEI' \
--to=sakamoto.kei@renesas.com \
--cc=gdb-patches@sources.redhat.com \
/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