genode

History

Martin Stein fbe9d26c47 trace: initialize trace control in Thread::start Previously, the trace control of a thread was initialized in its constructor (which is generic for all components). This has the disadvantage that the CPU-session-pointer member of the thread might not be valid at this point. And it cannot be replaced by using the "deprecated_env" CPU session neither as constructing the deprecated environment in causes troubles in Core. But as the trace control shouldn't be needed in Core anyway, the initialization can be moved to the Thread::start implementation of non-core components. This code already takes care of the CPU session pointer. Fixes #2901		2018-08-02 14:36:35 +02:00
..
etc	Let default tools.conf cover each architecture	2016-07-15 11:38:26 +02:00
include	trace: initialize trace control in Thread::start	2018-08-02 14:36:35 +02:00
lib	base: support to attach RAM dataspaces readonly	2018-05-30 13:36:27 +02:00
mk	base: remove cortex* compiler flags (fix #2787 )	2018-05-03 15:32:01 +02:00
ports	grub2: avoid switching modes	2018-06-12 12:11:44 +02:00
recipes	depot: update recipe hashes	2018-07-03 09:40:11 +02:00
run	Tweak run scripts for sel4 (caps, timeout)	2018-07-03 09:39:32 +02:00
src	trace: initialize trace control in Thread::start	2018-08-02 14:36:35 +02:00
README	core: add information about infos provided by core	2017-06-29 11:59:52 +02:00

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.

_Core_ may export information about the hardware platform by an ROM
called 'platform_info'. Depending on the platform, e.g. ARM or x86 or riscv,
and depending on the boot mode and boot loader and kernel, some nodes may not
be populated.

!<platform_info>
! <acpi revision="2" rsdt="0x1fe93074" xsdt="0x1fe930e8"/>
! <boot>
!   <framebuffer phys="0x7300000" width="1024" height="768" bpp="32"/>
! </boot>
!</platform_info>

If the ACPI RSDT and XSDT physical pointer is reported by the used kernel
and/or bootloader, _Core_ may provide this information by the ROM.

If the graphic device is initialised and can be directly used by a framebuffer
driver, _Core_ may provide the physical pointer to the framebuffer, the
resolution and color depth in bits.