c450ddcb3d
This patch removes possible ambiguities with respect to the naming of kernel-dependent binaries and libraries. It also removes the use of kernel-specific global side effects from the build system. The reach of kernel-specific peculiarities has thereby become limited to the actual users of the respective 'syscall-<kernel>' libraries. Kernel-specific build artifacts are no longer generated at magic places within the build directory (like okl4's includes, or the L4 build directories of L4/Fiasco and Fiasco.OC, or the build directories of various kernels). Instead, such artifacts have been largely moved to the libcache. E.g., the former '<build-dir>/l4/' build directory for the L4 build system resides at '<build-dir>/var/libcache/syscall-foc/build/'. This way, the location is unique to the kernel. Note that various tools are still generated somewhat arbitrarily under '<build-dir>/tool/' as there is no proper formalism for building host tools yet. As the result of this work, it has become possible to use a joint Genode build directory that is usable with all kernels of a given hardware platform. E.g., on x86_32, one can now seamlessly switch between linux, nova, sel4, okl4, fiasco, foc, and pistachio without rebuilding any components except for core, the kernel, the dynamic linker, and the timer driver. At the current stage, such a build directory must still be created manually. A change of the 'create_builddir' tool will follow to make this feature easily available. This patch also simplifies various 'run/boot_dir' plugins by removing the option for an externally hosted kernel. This option remained unused for many years now. Issue #2190 |
||
|---|---|---|
| .. | ||
| kdb | ||
| spec | ||
| main.cc | ||
| README | ||
| target.inc | ||
| uart_component.h | ||
| uart_driver_base.h | ||
This driver operates the UARTs on the given platform. It provides the 'Terminal_session' interface for output via serial line. Configuration ~~~~~~~~~~~~~ The server supports the following configuration options, supplied via Genode's config mechanism. :Routing clients to specific UARTs: Depending on the underlying hardware platform, the UART server is configurable to route specific clients to distinct UARTs. There is no default routing, so the configuration is mandatory. UART 0 is assumed to be used by the kernel and, therefore, left untouched. ! <config> ! <policy label_prefix="test-uart1" uart="1" detect_size="yes" /> ! <policy label_prefix="test-uart2" uart="2" /> ! <policy label_prefix="test-uartx" uart="1" /> ! </config> If the 'detect_size' attribute is set to "yes", the UART driver will try to detect the terminal size of the connected remote terminal using a protocol of escape sequences. If not specified, the UART driver will report a size of (0, 0) to the terminal-session client.