From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23978 invoked by alias); 28 Nov 2012 19:24:34 -0000 Received: (qmail 23961 invoked by uid 22791); 28 Nov 2012 19:24:32 -0000 X-SWARE-Spam-Status: No, hits=0.8 required=5.0 tests=AWL,BAYES_20,RCVD_IN_DNSWL_NONE,SARE_RECV_UK2NET2 X-Spam-Check-By: sourceware.org Received: from smtprelay0099.hostedemail.com (HELO smtprelay.hostedemail.com) (216.40.44.99) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 28 Nov 2012 19:24:27 +0000 Received: from filter.hostedemail.com (ff-bigip1 [10.5.19.254]) by smtprelay03.hostedemail.com (Postfix) with SMTP id B817494001 for ; Wed, 28 Nov 2012 19:24:26 +0000 (UTC) X-Panda: scanned! X-Session-Marker: 6A62656E6973746F6E40756B322E6E6574 X-Filterd-Recvd-Size: 1893 Received: from JonPC (cpc21-croy19-2-0-cust368.croy.cable.virginmedia.com [94.174.157.113]) (Authenticated sender: jbeniston@uk2.net) by omf11.hostedemail.com (Postfix) with ESMTPA for ; Wed, 28 Nov 2012 19:24:26 +0000 (UTC) From: "Jon Beniston" To: Subject: Memory-mapped peripheral registers, remote protocol and memory maps Date: Wed, 28 Nov 2012 19:24:00 -0000 Message-ID: <004701cdcd9d$e487ff90$ad97feb0$@beniston.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2012-11/txt/msg00085.txt.bz2 Hi, How is the access of memory-mapped peripheral registers handled over the remote protocol? By this, I mean how can you force a 32-bit read/write, rather than 4 byte accesses, to read/write a 32-bit memory-mapper register? I can see that you can define memory regions with the mem command, and set the memory access size to 32, but how does this map over the remote protocol? The remote protocol documentation for the 'm' packet says: "The stub need not use any particular size or alignment when gathering data from memory for the response; even if addr is word-aligned and length is a multiple of the word size, the stub is free to use byte accesses, or not. For this reason, this packet may not be suitable for accessing memory-mapped I/O devices.". Is there another packet that is suitable? It doesn't look like the code in remote.c uses this attribute. Also, in the documentation of the memory map format, it seems the only memory types are ram, rom and flash, with the only property being blocksize. Should there not be additional properties to correspond to the attributes supported by the mem command (i.e. an access size property)? Cheers, Jon