RE: [dsdp-tm-dev] TCF features - FileSystem

["Burton, Felix" <Felix.Burton@xxxxxxxxxxxxx>]

Hi Ed,

Thanks for your offer to contribute and your interest in TCF.

I am interested in your contribution, so if you could, please attach it
to a bugzilla entry.

One question that occurred to me when reading you email is if using mmap
to read/write is something one wants to do on a command by command basis
or more on a file by file basis.  If the latter is true, then it we
might consider adding a mode flag to open that specifies that mmap
should be used for read/write instead of having separate mmread/mmwrite
commands. 

Thoughts?
Felix

> -----Original Message-----
> From: dsdp-tm-dev-bounces@xxxxxxxxxxx [mailto:dsdp-tm-dev-
> bounces@xxxxxxxxxxx] On Behalf Of Swarthout Edward L-SWARTHOU
> Sent: Tuesday, September 23, 2008 8:59 AM
> To: Target Management developer discussions
> Subject: [dsdp-tm-dev] TCF features - FileSystem
> 
> We've added some features to the example TCF implementation and I
> wondered if there is interest in having them contributed back to
> eclipse?
> 
> Here are two of them:
> 
> 1. a client for the FileSystem service that transfers raw binary data
> to
> and from the agent via stdin and stdout.
> 
> Syntax: tcfraw filesystem_command agent:port agent_filename offset
> bytes
> <wordsize>
> 
> Example:
> 
> $ tcfraw read TCP:ds62:1534 /proc/cpuinfo 0 20
> processor	: 0
> cpu		: e500v2
> 
> 2. Add mmap mmread and mmwrite support to the FileSystem service.
> 
> There are some files in Linux that are only accessible from mmap (/sys
> device resource files)
> and some that are best accessed from mmap (/dev/mem).
> 
> Here's an example accessing a Linux-target physical memory:
> 
> $ tcfraw mmread TCP:ds62:1534 /dev/mem 0 20 1 | od -An -t x4
>  65642077 61732068 65726520 20202020
>  20202020 20202020 20202020 20202020
> 
> -EdS
> _______________________________________________
> dsdp-tm-dev mailing list
> dsdp-tm-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev