From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30138 invoked by alias); 9 Apr 2002 16:31:26 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 30122 invoked from network); 9 Apr 2002 16:31:24 -0000 Received: from unknown (HELO beta.dmz-eu.st.com) (164.129.1.35) by sources.redhat.com with SMTP; 9 Apr 2002 16:31:24 -0000 Received: from zeta.dmz-eu.st.com (zeta.dmz-eu.st.com [164.129.230.9]) by beta.dmz-eu.st.com (STMicroelectronics) with SMTP id C79E24CE1 for ; Tue, 9 Apr 2002 16:31:20 +0000 (GMT) Received: by zeta.dmz-eu.st.com (STMicroelectronics, from userid 0) id B47866203; Tue, 9 Apr 2002 16:31:20 +0000 (GMT) Received: from thistle.bri.st.com (localhost [127.0.0.1]) by zeta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 9CA841845 for ; Tue, 9 Apr 2002 16:31:19 +0000 (GMT) Received: from [164.129.8.14] (helo=masterwort) by thistle.bristol.st.com with esmtp (Exim 3.03 #5) id 16uyWb-0002dn-00 for gdb@sources.redhat.com; Tue, 09 Apr 2002 17:31:17 +0100 Received: from [164.129.14.48] (helo=sioux) by masterwort with asmtp (Exim 3.22 #1) id 16uyWb-0000Cz-00 for gdb@sources.redhat.com; Tue, 09 Apr 2002 17:31:17 +0100 Message-ID: <02f401c1dfe3$ffdcdf80$300e81a4@bri.st.com> From: "Paul Bartlett" To: Subject: Fw: gdbserver, remote serial protocol and endian issues Date: Tue, 09 Apr 2002 09:31:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-SW-Source: 2002-04/txt/msg00130.txt.bz2 ----- Original Message ----- From: "Paul Bartlett" To: 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 that > appear > in the memory map that *must* be written using the appropriate > access size. > > > Proposals for an extension to the protocol that implement this > 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 July > 2001 and then just disappeared completely. > > A cursory inspection of remote.c shows that the memory attribute > changes have made it down to remote_xfer_memory(). I presume > that all that needs to be done (for remote targets anyhow) is to > 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 > syntax. > > Does anybody have any opinions on which way to go from here? > > Paul > >