Add some ANSI C procedures to base-common
This is for the convenience of language runtimes.
|1 year ago|
|configs||1 year ago|
|depot||2 years ago|
|doc||1 year ago|
|repos||1 year ago|
|tool||1 year ago|
|.gitignore||1 year ago|
|.gitmodules||1 year ago|
|LICENSE||4 years ago|
|README.md||1 year ago|
|Tupfile.ini||1 year ago|
|Tuprules.gcc||1 year ago|
|Tuprules.llvm||1 year ago|
|Tuprules.tup||1 year ago|
|VERSION||1 year ago|
|flake.lock||1 year ago|
|flake.nix||1 year ago|
This a fork of the Genode OS reference implementation with a replacement build system that is humane and interoperable.
Changes against Genode Labs master may be reviewed with the following commands:
git remote add genodelabs https://github.com/genodelabs/genode.git git fetch genodelabs git diff genodelabs/master
This is the source tree of the reference implementation of the Genode OS architecture. For a general overview about the architecture, please refer to the project’s official website:
The current implementation can be compiled for 8 different kernels: Linux, L4ka::Pistachio, L4/Fiasco, OKL4, NOVA, Fiasco.OC, seL4, and a custom kernel for running Genode directly on ARM-based hardware. Whereas the Linux version serves us as development vehicle and enables us to rapidly develop the generic parts of the system, the actual target platforms of the framework are microkernels. There is no “perfect” microkernel - and neither should there be one. If a microkernel pretended to be fit for all use cases, it wouldn’t be “micro”. Hence, all microkernels differ in terms of their respective features, complexity, and supported hardware architectures.
Genode allows the use of each of the kernels listed above with a rich set of device drivers, protocol stacks, libraries, and applications in a uniform way. For developers, the framework provides an easy way to target multiple different kernels instead of tying the development to a particular kernel technology. For kernel developers, Genode contributes advanced workloads, stress-testing their kernel, and enabling a variety of application use cases that would not be possible otherwise. For users and system integrators, it enables the choice of the kernel that fits best with the requirements at hand for the particular usage scenario.
The primary documentation is the book “Genode Foundations”, which is available on the front page of Genode website:
The book describes Genode in a holistic and comprehensive way. It equips you with a thorough understanding of the architecture, assists developers with the explanation of the development environment and system configuration, and provides a look under the hood of the framework. Furthermore, it contains the specification of the framework’s programming interface.
The project has a quarterly release cycle. Each version is accompanied with detailed release documentation, which is available at the documentation section of the project website:
The source tree is composed of the following subdirectories:
This directory contains general documentation. Please consider the following document for a quick guide to get started with the framework:
If you are curious about the ready-to-use components that come with the framework, please review the components overview:
This directory contains the so-called source-code repositories of Genode. Please refer to the README file in the ‘repos’ directory to learn more about the roles of the individual repositories.
Source-code management tools and scripts. Please refer to the README file contained in the directory.
Local depot and public archive of Genode packages. Please refer to
for more details.
The components found within the main source tree are complemented by a growing library of additional software, which can be seamlessly integrated into Genode system scenarios.
The best way to get in touch with Genode developers and users is the project’s mailing list. Please feel welcome to join in!
The driving force behind the Genode OS Framework is the German company Genode Labs. The company offers commercial licensing, trainings, support, and contracted development work: