mirror of
https://github.com/genodelabs/genode.git
synced 2025-01-11 23:43:15 +00:00
f6dec901bb
It turns out that the name function does not have much use in practice except for naming the thread of the component's initial entrypoint. For dynamically linked components, this thread is created by the dynamic linker. It is named "ep" in these cases. Considering that we will eventually turn all regular components into dynamically linked executables, the additional information provided by the Component::name() function remains unused. So it is better to not bother the component developers with adding boilerplate code. |
||
|---|---|---|
| .. | ||
| etc | ||
| include | ||
| lib | ||
| mk | ||
| run | ||
| src | ||
| README | ||
This is generic part of the Genode implementation. It consists of two parts: :_Core_: is the ultimate root of the Genode application tree and provides abstractions for the lowest-level hardware resources such as RAM, ROM, CPU, and generic device access. All generic parts of Core can be found here - for system-specific implementations refer to the appropriate 'base-<system>' directory. :_Base libraries and protocols_: that are used by each Genode component to interact with other components. This is the glue that holds everything together.