mirror of
https://github.com/genodelabs/genode.git
synced 2025-04-10 04:41:13 +00:00
ad059362d2
For base-hw Core, we used to add quite some hardware-specific include paths to 'INC_DIR'. Generic code used to include, for instance, '<cpu.h>' and '<translation_table.h>' using these implicit path resolutions. This commit removes hardware-specific include paths except for 1) the '<board.h>' include paths (e.g., 'src/core/board/pbxa9'), 2) most architecture-specific include paths (e.g., 'src/core/spec/arm_v7'), 3) include paths that reflect usage of virtualization or ARM Trustzone (e.g., 'src/core/spec/arm/virtualization'). The first category is kept because, in contrast to the former "spec"-mechanism, the board variable used for this type of resolution is not deprecated and the board headers are meant to be the front end of hardware-specific headers towards generic code which is why they must be available generically via '<board.h>'. The second category is kept because it was suggested by other maintainers that simple arch-dependent headers (like for the declaration of a CPU state) should not imply the inclusion of the whole '<board.h>' and because the architecture is given also without the former "spec"-mechanism through the type of the build directory. I think this is questionable but am fine with it. The third category is kept because the whole way of saying whether virtualization resp. ARM Trustzone is used is done in an out-dated manner and changing it now would blow up this commit a lot and exceed the time that I'm willing to spend. This category should be subject to a future issue. Ref #4217
=================================
Genode Operating System Framework
=================================
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:
:Official project website for the Genode OS Framework:
[https://genode.org/documentation/general-overview]
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.
Documentation
#############
The primary documentation is the book "Genode Foundations", which is available
on the front page of Genode website:
:Download the book "Genode Foundations":
[https://genode.org]
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:
:Release documentation:
[https://genode.org/documentation/release-notes/]
Directory overview
##################
The source tree is composed of the following subdirectories:
:'doc':
This directory contains general documentation along with a comprehensive
collection of release notes.
:'repos':
This directory contains the source code, organized in so-called source-code
repositories. Please refer to the README file in the 'repos' directory to
learn more about the roles of the individual repositories.
:'tool':
Source-code management tools and scripts. Please refer to the README file
contained in the directory.
:'depot':
Directory used by Genode's package-management tools. It contains the public
keys and download locations of software providers.
Additional community-maintained components
##########################################
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.
:Genode-world repository:
[https://github.com/genodelabs/genode-world]
Contact
#######
The best way to get in touch with Genode developers and users is the project's
mailing list. Please feel welcome to join in!
:Genode Mailing Lists:
[https://genode.org/community/mailing-lists]
Commercial support
##################
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:
:Genode Labs website:
[https://www.genode-labs.com]