This is the mail archive of the
mailing list for the GDB project.
Fw: gdbserver, remote serial protocol and endian issues
- From: "Paul Bartlett" <paul dot bartlett at st dot com>
- To: <gdb at sources dot redhat dot com>
- Date: Tue, 9 Apr 2002 17:31:28 +0100
- Subject: Fw: gdbserver, remote serial protocol and endian issues
----- Original Message -----
From: "Paul Bartlett" <firstname.lastname@example.org>
Sent: Tuesday, April 09, 2002 5:28 PM
Subject: Re: gdbserver, remote serial protocol and endian issues
> > I assume you mean something like a memory read at &foo only
> works if
> > done as a 16 bit operation by the remote target.
> Yes. There are certain configuration registers for SH4/SH5
> in the memory map that *must* be written using the appropriate
> access size.
> > Proposals for an extension to the protocol that implement
> have been
> > posted (search for e-mail from jtc). The memory attribute
> framework was
> > introduced in preparation for this.
> I've spent a good proportion of the day trawling the list
> archives for JT Conklin's stuff.
> I noticed that he was a prolific contributor up to about 16
> 2001 and then just disappeared completely.
> A cursory inspection of remote.c shows that the memory
> changes have made it down to remote_xfer_memory(). I presume
> that all that needs to be done (for remote targets anyhow) is
> come up with suitable changes to the rsp and propagate the
> parameters through.
> I see that one of JT's last contributions was a suggested
> Does anybody have any opinions on which way to go from here?