genode/repos/base
Christian Helmuth cbfec0deed ldso: check ctors sections of shared-object deps
The sole existence of shared-object dependencies lead to fatal
static-constructor errors before. Now, ldso checks if the ctors section
of objects in the init list are non-empty before whining.

Issue #2759
2018-05-30 12:26:18 +02:00
..
etc Let default tools.conf cover each architecture 2016-07-15 11:38:26 +02:00
include trace/buffer: keep "last" entry on wraps 2018-05-03 15:31:54 +02:00
lib timeout: become independent of the Alarm framework 2018-04-10 11:11:54 +02:00
mk base: remove cortex* compiler flags (fix #2787) 2018-05-03 15:32:01 +02:00
ports grub2: update to fix boots without using bender 2018-03-29 14:59:05 +02:00
recipes depot: update recipe hashes 2018-05-03 15:32:01 +02:00
run ada: runtime and library support 2018-04-19 12:38:54 +02:00
src ldso: check ctors sections of shared-object deps 2018-05-30 12:26:18 +02:00
README core: add information about infos provided by core 2017-06-29 11:59:52 +02:00

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.