<!--

Test configuration for nested Init processes
============================================

The config node of each start entry shadows the
'config' ROM file for the corresponding process.
This way, an arbitrarily complex process tree
can be described by only one central configuration
file:

  <config>
    <start...>
      ...
      <config>
        ...
        ...
      </config>
    </start>
  <config>

Alternatively, a separate file can be specified
as configuration for a start entry by using
the 'configfile' tag:

  <config>
    <start...>
      ...
      <configfile>another_config</configfile>
    </start>
  <config>

-->

<config>
	<parent-provides>
		<service name="CAP"/>
		<service name="LOG"/>
		<service name="ROM"/>
		<service name="RAM"/>
		<service name="CPU"/>
		<service name="RM"/>
		<service name="PD"/>
	</parent-provides>
	<start name="timer">
		<resource name="RAM" quantum="1M"/>
		<provides><service name="Timer"/></provides>
		<route>
			<service name="CAP"> <parent/> </service>
		</route>
	</start>
	<start name="init">
		<resource name="RAM" quantum="1M"/>
		<config>
			<parent-provides>
				<service name="Timer"/>
				<service name="LOG"/>
			</parent-provides>
			<start name="test-timer">
				<resource name="RAM" quantum="1M"/>
				<route>
					<service name="Timer"> <parent/> </service>
					<service name="LOG">   <parent/> </service>
				</route>
			</start>
		</config>
		<route>
			<service name="Timer"> <child name="timer"/> </service>
			<service name="LOG">   <parent/>             </service>
			<service name="ROM">   <parent/>             </service>
			<service name="RAM">   <parent/>             </service>
			<service name="CAP">   <parent/>             </service>
			<service name="CPU">   <parent/>             </service>
			<service name="RM">    <parent/>             </service>
			<service name="PD">    <parent/>             </service>
		</route>
	</start>
</config>

