From: "Kei Sakamoto" <sakamoto.kei@renesas.com>
To: <gdb-patches@sources.redhat.com>
Subject: Re: [patch] New m32r remote target, m32rsdi
Date: Fri, 05 Sep 2003 02:59:00 -0000 [thread overview]
Message-ID: <012d01c37359$e3f98510$5169910a@KEI> (raw)
In-Reply-To: <01af01c3679d$25650650$5169910a@KEI>
Hello,
I posted the following two weeks ago, but there is no reaction
so far.
Its patch adds a new remote protocol to m32r architecture and
does not influence any other functions. So I think it's safe
to add.
I'm going to commit it next weak. Please let me know if there
is any problem.
Kei Sakamoto
From: "Kei Sakamoto" <sakamoto.kei@renesas.com>
To: "Daniel Jacobowitz" <drow@mvista.com>
Cc: <gdb-patches@sources.redhat.com>
Sent: Thursday, August 21, 2003 1:31 PM
Subject: Re: [patch] New m32r remote target, m32rsdi
> > On Mon, Aug 04, 2003 at 05:00:55PM +0900, Kei Sakamoto wrote:
> > > Hello,
> > >
> > > The attached adds a new remote target, m32rsdi, which uses
> > > m32r's on-chip debug interface, SDI (Scalable Debug Interface).
> > >
> > > In m32rsdi target mode, gdb does not control a target board
> > > directly. Instead, gdb sends commands to "sdiserver" by sockets
> > > interface. Sdiserver is a program which controls the target
> > > board using printer ports.
> > >
> > > Is this OK to commit?
> > >
> > > Kei Sakamoto
> > >
> > > ====
> > >
> > > 2003-08-04 Kei Sakamoto <sakamoto.kei@renesas.com>
> > >
> > >
> > > * remote-m32r-sdi.c : New file, interface to m32r on-chip
> > > debug interface, SDI (Scalable Debug Interface).
> > > * Makefile.in (remote-m32r-sdi.o): Add build rule.
> > > * config/m32r/m32r.mt (TDEPFILES) : Add remote-m32r-sdi.o.
> >
> > I don't feel qualified to review a new remote target, so you'll have to
> > ask the remote maintainer. However, there's definitely a problem with
> > the new code. It's full of pieces like:
> >
> > if (TARGET_BYTE_ORDER == BFD_ENDIAN_BIG)
> > *((unsigned long *) (buf + 1)) = pc_addr;
> > else
> > *((unsigned long *) (buf + 1)) = pc_addr - 1;
> >
> > This sends host-endian data over the wire to the target. Run it on a
> > big-endian host and bad things will happen.
>
> Thank you for reviewing my patch. I revised it and removed
> the endian problem.
>
> I've tested the attached patch on both Linux/Pentium-III and
> Soralis/Sparc4. So it works fine on both little-endian host
> and big-endian host.
>
> Kei Sakamoto
>
> ====
>
> 2003-08-21 Kei Sakamoto <sakamoto.kei@renesas.com>
>
> * remote-m32r-sdi.c : New file, interface to m32r on-chip
> debug interface, SDI (Scalable Debug Interface).
> * Makefile.in (remote-m32r-sdi.o): Add build rule.
> * config/m32r/m32r.mt (TDEPFILES) : Add remote-m32r-sdi.o.
>
next prev parent reply other threads:[~2003-09-05 2:59 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 [this message]
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
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='012d01c37359$e3f98510$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