alex/genode-world
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

remote_rom: minor README tweaks

Browse Source
This commit is contained in:
Norman Feske
2016-08-26 11:26:10 +02:00
parent 4182330914
commit 5e54c04b1c
1 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
src/proxy/remote_rom/README
View File

@@ -8,25 +8,25 @@ the specified backend and provides a ROM service via local RPC.
Backends
--------
The remote_rom can be compiled with one of multiple backends that use different session
The remote_rom can be compiled with one of multiple back ends that use different session
interfaces or libraries to forward and receive the packets. By exchanging the backend,
we can also easily change the publication strategy (e.g. notification+polling vs. multicast).
Furthermore, a backend is responsible for access control and optionally allows the
we can also easily change the publication strategy (e.g., notification+polling vs. multicast).
Furthermore, a back end is responsible for access control and optionally allows the
specification of a policy for this.
:'nic_ip':
This backend uses a Nic_session to transmit network packets with IPv4 headers.
This back end uses a Nic_session to transmit network packets with IPv4 headers.
Configuration
-------------
Both, the client and the server evaluate the <remote_rom> node of their config.
The _name_ attribute specifies the ROMs module name. The <remote_rom> node may
further contain a <default> node that can be used to populate the ROM with a default
Both the client and the server evaluate the '<remote_rom>' node of their config.
The _name_ attribute specifies the ROMs module name. The '<remote_rom>' node may
further contain a '<default>' node that can be used to populate the ROM with a default
content.
Example
~~~~~~~
For an example that illustrates the use of these components, please refer to the
_run/test-remote_rom_backend_nic.run_ script.
_run/remote_rom_backend_nic_ip.run_ script.