From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,98e311935a219163
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2002-05-28 10:52:51 PST
Path: archiver1.google.com!postnews1.google.com!not-for-mail
From: John_J_Cupak@raytheon.com (John Cupak)
Newsgroups: comp.lang.ada
Subject: Re: Help with Copying Shared Memory to Local
Date: 28 May 2002 10:52:51 -0700
Organization: http://groups.google.com/
Message-ID: <c7990eda.0205280952.104ba8cf@posting.google.com>
References: <c7990eda.0205230550.203d300a@posting.google.com>
 <3CED51CF.39E26FC6@acm.org> <u0dH8.6904$AJ5.1584062@typhoon.ne.ipsvc.net>
 <uer6almsiuh145@corp.supernews.com> <3CEDA095.61BE6EF6@acm.org>
 <478AE9B914ED6844.5DEC7C5E64D6473E.909AD32BDF37CFA7@lp.airnews.net>
 <hoWH8.4604$jv5.1045024@typhoon.ne.ipsvc.net>
NNTP-Posting-Host: 199.46.198.231
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1022608371 16936 127.0.0.1 (28 May 2002 17:52:51
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: 28 May 2002 17:52:51 GMT
Xref: archiver1.google.com comp.lang.ada:24871
Date: 2002-05-28T17:52:51+00:00
List-Id: <comp.lang.ada>

"John Cupak" <Jcupak744@attbi.com> wrote in message news:<hoWH8.4604$jv5.1045024@typhoon.ne.ipsvc.net>...
> Jeffry, et al,
> 
> As this is Memorial Day weekend, and I'm not at work, I can't ask the person
> who brought this problem
> to my attention just what processor they're using. But, I suspect that this
> is a very restricted embedded
> processor/system and that the timing/chip/etc problem is VERY applicable to
> the solution here.
> 
> When I get into work on Tuesday, I'll ask for hardware details - something I
> (a poor software engineer)
> forgot to do when presented with the problem.
> 
> John

Well, I talked to the programmer who posed this problem to me, and he
said that the computer hardware is "Standard VME", but that the shared
memory card is old, poorly-documented, and "home-brewed". He promised
to get me what information he can on the memory card in a day or so.

He also mentioned when he created two byte arrays and mapped them to
the shared and local memory, the compiler would NOT let him write
A:=B, but he COULD write A(I):=B(I), where the index, I, was a
double-byte index. I suspect there's some 16-bit addressing / transfer
going on at the hardware board level.

We'll know more in a day or two.

John