2018-01-19 12:30:42 +00:00
|
|
|
<runtime ram="32M" caps="1000" binary="init">
|
2017-07-05 08:39:59 +00:00
|
|
|
|
2018-01-29 10:46:52 +00:00
|
|
|
<requires> <timer/> </requires>
|
2017-07-05 08:39:59 +00:00
|
|
|
|
2018-10-08 12:04:43 +00:00
|
|
|
<events>
|
|
|
|
<timeout meaning="failed" sec="10" />
|
|
|
|
<log meaning="succeeded">child "test-fs_report" exited with exit value 0</log>
|
|
|
|
<log meaning="failed" >child "test-fs_report" exited with exit value -1</log>
|
|
|
|
</events>
|
|
|
|
|
2018-01-29 10:46:52 +00:00
|
|
|
<content>
|
|
|
|
<rom label="ld.lib.so"/>
|
|
|
|
<rom label="ram_fs"/>
|
|
|
|
<rom label="fs_report"/>
|
|
|
|
<rom label="fs_rom"/>
|
|
|
|
<rom label="test-fs_report"/>
|
2018-04-23 08:49:21 +00:00
|
|
|
<rom label="vfs.lib.so"/>
|
2018-01-29 10:46:52 +00:00
|
|
|
</content>
|
2017-07-05 08:39:59 +00:00
|
|
|
|
|
|
|
<config>
|
|
|
|
<parent-provides>
|
|
|
|
<service name="CPU"/>
|
|
|
|
<service name="LOG"/>
|
|
|
|
<service name="PD"/>
|
|
|
|
<service name="ROM"/>
|
2017-07-05 08:40:29 +00:00
|
|
|
<service name="Timer"/>
|
2017-07-05 08:39:59 +00:00
|
|
|
</parent-provides>
|
|
|
|
|
|
|
|
<default-route>
|
|
|
|
<any-service> <parent/> <any-child/> </any-service>
|
|
|
|
</default-route>
|
|
|
|
|
|
|
|
<default caps="100"/>
|
|
|
|
|
|
|
|
<start name="ram_fs">
|
|
|
|
<resource name="RAM" quantum="4M"/>
|
|
|
|
<provides> <service name="File_system"/> </provides>
|
|
|
|
<config>
|
|
|
|
<content>
|
|
|
|
<dir name="test-fs_report">
|
|
|
|
<inline name="devices">
|
|
|
|
<devices version="initial"/>
|
|
|
|
</inline>
|
|
|
|
</dir>
|
|
|
|
</content>
|
|
|
|
<policy label_prefix="fs_report -> " root="/" writeable="yes"/>
|
|
|
|
<policy label_prefix="fs_rom -> " root="/test-fs_report"/>
|
2018-05-27 08:09:00 +00:00
|
|
|
<policy label_prefix="test-fs_report -> " root="/test-fs_report" writeable="yes"/>
|
2017-07-05 08:39:59 +00:00
|
|
|
</config>
|
|
|
|
</start>
|
|
|
|
<!--
|
|
|
|
All reports sent by 'test-fs_report' are prefixed with the label of the
|
|
|
|
component. Hence, they are written to the 'test-fs_report/' subdirectory.
|
|
|
|
-->
|
|
|
|
<start name="fs_report">
|
|
|
|
<resource name="RAM" quantum="4M"/>
|
|
|
|
<provides> <service name="Report"/> </provides>
|
|
|
|
<config> <vfs> <fs/> </vfs> </config>
|
|
|
|
</start>
|
|
|
|
<start name="fs_rom">
|
|
|
|
<resource name="RAM" quantum="4M"/>
|
|
|
|
<provides> <service name="ROM"/> </provides>
|
|
|
|
<config/>
|
|
|
|
</start>
|
|
|
|
<start name="test-fs_report">
|
|
|
|
<resource name="RAM" quantum="4M"/>
|
2018-05-27 08:09:00 +00:00
|
|
|
<config> <vfs> <fs/> </vfs> </config>
|
2017-07-05 08:39:59 +00:00
|
|
|
<route>
|
|
|
|
<service name="ROM" label="devices"> <child name="fs_rom"/> </service>
|
|
|
|
<service name="ROM" label="focus"> <child name="fs_rom"/> </service>
|
|
|
|
<service name="Report" label="devices"> <child name="fs_report"/> </service>
|
|
|
|
<service name="Report" label="focus"> <child name="fs_report"/> </service>
|
|
|
|
<any-service> <parent/> <any-child/> </any-service>
|
|
|
|
</route>
|
|
|
|
</start>
|
|
|
|
</config>
|
|
|
|
</runtime>
|