From 371c11829f1a6179f96ba4035bc21c708ceacfda Mon Sep 17 00:00:00 2001 From: Norman Feske Date: Wed, 27 Feb 2013 15:00:48 +0100 Subject: [PATCH] doc: Update components.txt --- doc/components.txt | 47 ++++++++++++++++++++++++---------------------- 1 file changed, 25 insertions(+), 22 deletions(-) diff --git a/doc/components.txt b/doc/components.txt index 2f868be13..ae77ff8ec 100644 --- a/doc/components.txt +++ b/doc/components.txt @@ -139,26 +139,21 @@ input-session interfaces respectively. Timer drivers ============= -All timer drivers implement the timer-session interface. Technically, a timer -driver is both a device driver (accessing a timer device) and a resource -multiplexer (supporting multiple timer-session clients at the same time). The -timer implementations differ in their use of different time sources and the -mode of internal operation of the timer sessions. Time sources are either -hardware timers, a time source provided by the kernel, or a pseudo time source -(busy). +The timer driver located at 'os/src/drivers/timer' implements the timer-session +interface. Technically, it is is both a device driver (accessing a timer +device) and a resource multiplexer (supporting multiple timer-session clients +at the same time). Depending on the base platform, the implementation uses of +different time sources. Time sources are either hardware timers, a time source +provided by the kernel, or a pseudo time source (busy): -The internal operation of the timer session depends on the kernel. On kernels -with support for out-of-order RPCs, all timer sessions are handled by a single -thread. Otherwise, each timer session uses a dedicated thread. - -:'timer/nova': PIT as time source, multi-threaded -:'timer/codezero': busy time source, single-threaded -:'timer/okl4_arm': busy time source, single-threaded -:'timer/okl4_x86': PIT as time source, single-threaded -:'timer/foc': IPC timeout as time source, multi-threaded -:'timer/fiasco': IPC timeout as time source, single-threaded -:'timer/pistachio': IPC timeout as time source, single-threaded -:'timer/linux': nanosleep as time source, single-threaded +:'nova': PIT as time source +:'codezero': busy time source +:'okl4_arm': busy time source +:'okl4_x86': PIT as time source +:'foc': IPC timeout as time source +:'fiasco': IPC timeout as time source +:'pistachio': IPC timeout as time source +:'linux': nanosleep as time source Audio output drivers @@ -269,6 +264,11 @@ subdirectory of a source repository. concurrently access the same FFAT-formatted block device. It is located at 'libports/src/server/ffat_fs'. +:Terminal: The terminal_mux service located at gems/src/server/terminal_mux + is able to provide multiple terminal sessions over one terminal-client + session. The user can switch between the different sessions using a keyboard + shortcut, which brings up an ncurses-based menu. + Protocol stacks ############### @@ -334,6 +334,11 @@ Separate components: A block service that fetches a virtual block device over the network from a HTTP server. +:'fs_rom': + A ROM service that translates the 'File_system' session interface to the + 'ROM' session' interface. Each request for a ROM file is handled by looking + up an equally named file on the file system. + Libraries: :'libports/lib/mk/libc': @@ -454,9 +459,7 @@ Runtime environments :'ports/src/vancouver': Vancouver is a virtual-machine monitor developed for the use with the NOVA platform. It virtualizes 32bit x86 PC hardware - including various peripherals. The current version is regarded as work in - progress. It is able to bootstrap one of the Fiasco or Pistachio kernels - but support for interrupts (i.e., the timer) is not yet implemented. + including various peripherals. :'os/src/server/loader': A service that allows the creation and destruction of Genode subsystems via a session interface. For further information,