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=unavailable autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Adam Jensen <hanzer@riseup.net>
Newsgroups: comp.lang.ada
Subject: Re: Getting started with bare-board development
Date: Sun, 13 Nov 2016 15:03:38 -0500
Organization: A noiseless patient Spider
Message-ID: <o0agtr$2gg$1@dont-email.me>
References: <o05g4n$q11$1@dont-email.me> <o06obm$u1b$1@dont-email.me>
 <o07f4o$9r4$1@dont-email.me> <o08oi5$bo4$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 13 Nov 2016 20:03:07 -0000 (UTC)
Injection-Info: mx02.eternal-september.org;
 posting-host="886269296a8927a8e422a267cc77681a";
	logging-data="2576"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX19tQ4Ghrtc97jn/C0puC7av"
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.4.0
In-Reply-To: <o08oi5$bo4$1@dont-email.me>
Cancel-Lock: sha1:HaG2MPWvCrN56jvBdbB8Xch7uls=
Xref: news.eternal-september.org comp.lang.ada:32299
Date: 2016-11-13T15:03:38-05:00
List-Id: <comp.lang.ada>

On 11/12/2016 11:01 PM, Jeffrey R. Carter wrote:
[snip]
> Then, for each intended H/W device, I write a pkg spec for a H/W-leaning
> interface. This reflects the capabilities and features of the device.
[snip]
> When it's time to run the S/W on the real system, you eliminate the
> environment pkg and replace the H/W I/F bodies with ones that actually
> I/F with the H/W. Note that the only differences between the simulated
> and actual systems are those bodies.

When writing device drivers, how do you mock the memory map of the
target hardware?

In the mocked the hardware, how is timing controlled?

When extending and mapping run-time support to the mocked hardware, how
does that fit into the run-time system for the native platform (your
workstation)?