From 0e7f50da78982a93a4603cddbb2e0c07019e9c1a Mon Sep 17 00:00:00 2001 From: Ulrich Weigand Date: Tue, 12 Jun 2007 14:38:32 +0000 Subject: ChangeLog: * remote.c (remote_write_qxfer): New function. (remote_xfer_partial): Add handling for TARGET_OBJECT_SPU. (remote_read_qxfer): Do not cache empty objects. (_initialize_remote): Add PACKET_qXfer_spu_read and PACKET_qXfer_spu_write. doc/ChangeLog: * gdb.texinfo (General Query Packets): Document qXfer:spu:read and qXfer:spu:write packets and mention them under qSupported. gdbserver/ChangeLog: * remote-utils.c (decode_xfer_write): New function. * server.h (decode_xfer_write): Add prototype. * server.c (handle_query): Add PACKET_LEN argument. Support qXfer:spu:read and qXfer:spu:write packets. (main): Pass packet_len to handle_query. * spu-low.c (spu_target_ops): Add spu_proc_xfer_spu. * target.h (target_ops): Add qxfer_spu. --- gdb/doc/ChangeLog | 6 ++++++ gdb/doc/gdb.texinfo | 54 +++++++++++++++++++++++++++++++++++++++++++++++------ 2 files changed, 54 insertions(+), 6 deletions(-) (limited to 'gdb/doc') diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index 7a73f3b..7c1850d 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,6 +1,12 @@ 2007-06-12 Ulrich Weigand Markus Deuling + * gdb.texinfo (General Query Packets): Document qXfer:spu:read + and qXfer:spu:write packets and mention them under qSupported. + +2007-06-12 Ulrich Weigand + Markus Deuling + * gdb.texinfo (Architectures): Add new SPU section to document Cell Broadband Engine SPU architecture specific commands. diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 0641386..5a3b0a9 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -23634,6 +23634,16 @@ These are the currently defined stub features and their properties: @tab @samp{-} @tab Yes +@item @samp{qXfer:spu:read} +@tab No +@tab @samp{-} +@tab Yes + +@item @samp{qXfer:spu:write} +@tab No +@tab @samp{-} +@tab Yes + @item @samp{QPassSignals} @tab No @tab @samp{-} @@ -23667,6 +23677,14 @@ The remote stub understands the @samp{qXfer:features:read} packet The remote stub understands the @samp{qXfer:memory-map:read} packet (@pxref{qXfer memory map read}). +@item qXfer:spu:read +The remote stub understands the @samp{qXfer:spu:read} packet +(@pxref{qXfer spu read}). + +@item qXfer:spu:write +The remote stub understands the @samp{qXfer:spu:write} packet +(@pxref{qXfer spu write}). + @item QPassSignals The remote stub understands the @samp{QPassSignals} packet (@pxref{QPassSignals}). @@ -23752,7 +23770,7 @@ packets.) Read uninterpreted bytes from the target's special data area identified by the keyword @var{object}. Request @var{length} bytes starting at @var{offset} bytes into the data. The content and -encoding of @var{annex} is specific to the object; it can supply +encoding of @var{annex} is specific to @var{object}; it can supply additional details about what data to access. Here are the specific requests of this form defined so far. All @@ -23785,6 +23803,17 @@ annex part of the generic @samp{qXfer} packet must be empty This packet is not probed by default; the remote stub must request it, by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}). + +@item qXfer:spu:read:@var{annex}:@var{offset},@var{length} +@anchor{qXfer spu read} +Read contents of an @code{spufs} file on the target system. The +annex specifies which file to read; it must be of the form +@file{@var{id}/@var{name}}, where @var{id} specifies an SPU context ID +in the target process, and @var{name} identifes the @code{spufs} file +in that context to be accessed. + +This packet is not probed by default; the remote stub must request it, +by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}). @end table Reply: @@ -23822,14 +23851,27 @@ the stub, or that the object does not support reading. @cindex write data into object, remote request Write uninterpreted bytes into the target's special data area identified by the keyword @var{object}, starting at @var{offset} bytes -into the data. @samp{@var{data}@dots{}} is the binary-encoded data +into the data. @var{data}@dots{} is the binary-encoded data (@pxref{Binary Data}) to be written. The content and encoding of @var{annex} -is specific to the object; it can supply additional details about what data +is specific to @var{object}; it can supply additional details about what data to access. -No requests of this form are presently in use. This specification -serves as a placeholder to document the common format that new -specific request specifications ought to use. +Here are the specific requests of this form defined so far. All +@samp{qXfer:@var{object}:write:@dots{}} requests use the same reply +formats, listed below. + +@table @samp +@item qXfer:@var{spu}:write:@var{annex}:@var{offset}:@var{data}@dots{} +@anchor{qXfer spu write} +Write @var{data} to an @code{spufs} file on the target system. The +annex specifies which file to write; it must be of the form +@file{@var{id}/@var{name}}, where @var{id} specifies an SPU context ID +in the target process, and @var{name} identifes the @code{spufs} file +in that context to be accessed. + +This packet is not probed by default; the remote stub must request it, +by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}). +@end table Reply: @table @samp -- cgit v1.1