genode

History

Tomasz Gajewski 870d348d77 trace: redirect logs to trace based on policy If trace is enabled for component than an attempt to put message into trace buffer is performed using log_output policy. If it succeeds than message is not put to logs using log service. Fixes #3714		2020-04-17 12:47:48 +02:00
..
etc	tools.conf: fix check for arm_64	2019-11-19 14:17:29 +01:00
include	trace: redirect logs to trace based on policy	2020-04-17 12:47:48 +02:00
lib	libc: provide C++ runtime symbols in ABI	2020-04-17 12:40:13 +02:00
mk	Retire OMAP4 support	2020-04-17 12:39:32 +02:00
ports	base: add uboot for imx8 as port	2019-12-19 17:01:42 +01:00
recipes	depot: update recipe hashes	2020-04-17 12:40:13 +02:00
run	Retire OMAP4 support	2020-04-17 12:39:32 +02:00
src	trace: redirect logs to trace based on policy	2020-04-17 12:47:48 +02:00
xsd	base_types.xsd: allow session labels of length 0	2018-11-16 14:37:19 +01: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.