genode

Fork of the Genode OS framework

Go to file

Martin Stein e7d57ded36 hw & trustzone: fix alignm. of VM exception-vector After modifying mode transition for branch prediction tz_vmm wasn't working anymore on hw_imx53_tz but the modifications had nothing to do with the VM code. However, the amount of instructions in the MT before the VM exception-vector changed. So I tried stuffing the last working version with NOPs and found that tz_vmm worked for some NOP amounts and for others not. Thus, I increased the alignment of the VM exception-vector from 16 bytes to 32 bytes, é voila, its working with any amount of NOPs as well as with branch prediction commits. ref #474		2014-08-15 10:19:49 +02:00
doc	doc: markup-fix in doc/porting_guide.txt	2014-05-29 13:55:27 +02:00
repos	hw & trustzone: fix alignm. of VM exception-vector	2014-08-15 10:19:49 +02:00
tool	tool chain: disable -Werror for building GDB	2014-07-24 10:18:08 +02:00
.gitignore	base-nova: migrate to new ports mechanism	2014-05-27 11:14:43 +02:00
LICENSE	Imported Genode release 11.11	2011-12-22 16:19:25 +01:00
README	Move repositories to 'repos/' subdirectory	2014-05-14 16:08:00 +02:00
VERSION	version: 14.05	2014-05-28 15:54:27 +02:00

README

                      =================================
                      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:

  [http://genode.org/documentation/general-overview]

The current implementation can be compiled for 8 different kernels: Linux,
L4ka::Pistachio, L4/Fiasco, OKL4, NOVA, Fiasco.OC, Codezero, 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.


Directory overview
##################

The source tree is composed of the following subdirectories:

:'doc':

  This directory contains general documentation. Please consider the following
  document for a quick guide to get started with the framework:

  ! doc/getting_started.txt

  If you are curious about the ready-to-use components that come with the
  framework, please review the components overview:

  ! doc/components.txt

:'repos':

  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.

:'tool':

  Source-code management tools and scripts. Please refer to the README file
  contained in the directory.


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:

  [http://genode.org/community/mailing-lists]