9a00ad7ae3
This patch introduces support for ROM sessions that update their provided data during the lifetime of the session. The 'Rom_session' interface had been extended with the new 'release()' and 'sigh()' functions, which are needed to support the new protocol. All ROM services have been updated to the new interface. Furthermore, the patch changes the child policy of init with regard to the handling of configuration files. The 'Init::Child' used to always provide the ROM dataspace with the child's config file via a locally implemented ROM service. However, for dynamic ROM sessions, we need to establish a session to the real supplier of the ROM data. This is achieved by using a new 'Child_policy_redirect_rom_file' policy to handle the 'configfile' rather than handling the 'configfile' case entirely within 'Child_config'. To see the new facility in action, the new 'os/run/dynamic_config.run' script provides a simple scenario. The config file of the test program is provided by a service, which generates and updates the config data at regular intervals. In addition, new support has been added to let slaves use dynamic reconfiguration. By using the new 'Child_policy_dynamic_rom_file', the configuration of a slave can be changed dynamically at runtime via the new 'configure()' function. The config is provided as plain null-terminated string (instead of a dataspace capability) because we need to buffer the config data anyway. So there is no benefit of using a dataspace. For buffering configuration data, a 'Ram_session' must be supplied. If no 'Ram_session' is specified at construction time of a 'Slave_policy', no config is supplied to the slave (which is still a common case). An example for dynamically reconfiguring a slave is provided by 'os/run/dynamic_config_slave.run'. |
||
|---|---|---|
| .. | ||
| doc | ||
| include/noux_session | ||
| lib/mk | ||
| mk | ||
| ports | ||
| run | ||
| src | ||
| Makefile | ||
| README | ||
This directory contains ports of popular 3rd-party applications to Genode. The 'ports' repository follows the line of the 'libports' repository. For instructions about downloading and building 3rd-party applications, please refer to 'libports/README'. Dependencies from other repositories ------------------------------------ Application provided by the 'ports' repository typically expect a rich runtime environment, including shared libraries provided by the 'libports' repository. Hence, 'ports' depends on 'libports'. Furthermore, applications may require additional repositories. For example, the Arora web browser depends on the 'qt4' repository.