doc: update README, components.txt etc.
This commit is contained in:
@@ -79,6 +79,14 @@ Platform devices
|
||||
this simple ACPI parser traverses the ACPI tables and reports device-resource
|
||||
information (e.g., interrupt lines of PCI devices).
|
||||
|
||||
:'libports/src/app/acpica':
|
||||
In addition to our ACPI base driver, the acpica component uses the
|
||||
ACPICA library to provide access to dynamic functions like battery
|
||||
states, events (e.g., notebook lid close and power buttons), as well
|
||||
as reset and power off. The componenten reports ACPI events and
|
||||
states as reports and itself responds to system state changes of
|
||||
certain configuration ROMs.
|
||||
|
||||
|
||||
UART devices
|
||||
============
|
||||
@@ -169,13 +177,13 @@ at the same time). Depending on the base platform, the implementation uses
|
||||
different time sources. Time sources are either hardware timers, a time source
|
||||
provided by the kernel, or a pseudo time source (busy):
|
||||
|
||||
:'nova': NOVA kernel semaphores as time source
|
||||
:'okl4_x86': PIT as time source
|
||||
:'foc': IPC timeout as time source
|
||||
:'fiasco': IPC timeout as time source
|
||||
:'pistachio': IPC timeout as time source
|
||||
:'linux': nanosleep as time source
|
||||
:'hw': hardware timers depending on platform, e.g., PIT on x86
|
||||
:'nova': NOVA kernel semaphores
|
||||
:'okl4_x86': Programmable Interval Timer (PIT) device
|
||||
:'foc': IPC timeout
|
||||
:'fiasco': IPC timeout
|
||||
:'pistachio': IPC timeout
|
||||
:'linux': nanosleep()
|
||||
:'hw': kernel timer
|
||||
|
||||
|
||||
Audio drivers
|
||||
@@ -461,9 +469,6 @@ Libraries:
|
||||
:'libports/lib/mk/libc':
|
||||
C runtime ported from FreeBSD.
|
||||
|
||||
:'libports/lib/mk/libc_log':
|
||||
Redirects the standard output of the libc to Genode's LOG session interface.
|
||||
|
||||
:'libports/lib/mk/libc_lwip_nic_dhcp':
|
||||
Translates the BSD socket API to a NIC session using the lwIP stack.
|
||||
|
||||
@@ -479,13 +484,6 @@ Libraries:
|
||||
:'libports/lib/mk/libc_fuse_ext2':
|
||||
Accesses files on a block device that contains an ext2 file system.
|
||||
|
||||
:'libports/lib/mk/libc_fs':
|
||||
Allows libc-using programs to access the Genode file-system infrastructure
|
||||
using the POSIX file API.
|
||||
|
||||
:'libports/lib/mk/libc_block':
|
||||
Accesses a block session as a virtual block device.
|
||||
|
||||
:'libports/lib/mk/libc_terminal':
|
||||
Connects the standard input and output from/to Genode's terminal session
|
||||
interface.
|
||||
|
||||
@@ -13,7 +13,7 @@ should be documented but isn't? Or the documentation contains errors with
|
||||
regard to content or spelling? Please let us know by raising the issue at the
|
||||
genode-main mailing list:
|
||||
|
||||
:[http://genode.org/community/mailing-lists - Genode mailing lists]:
|
||||
:[https://genode.org/community/mailing-lists - Genode mailing lists]:
|
||||
|
||||
If you are interested in getting your hands dirty with working on the Genode
|
||||
code base or authoring additional documentation, you are more than welcome.
|
||||
@@ -31,9 +31,9 @@ Alternatively, you may like to have a look at our road map and future
|
||||
challenges to see the big picture of our developments and to get inspiration
|
||||
for your own activities:
|
||||
|
||||
:[http://genode.org/about/road-map]: Road Map
|
||||
:[https://genode.org/about/road-map]: Road Map
|
||||
|
||||
:[http://genode.org/about/challenges]: Future Challenges
|
||||
:[https://genode.org/about/challenges]: Future Challenges
|
||||
|
||||
Once you settled on a specific topic to work on, it is a good idea to get
|
||||
acquainted with the work flow and tools used by the project. The following
|
||||
@@ -81,7 +81,7 @@ Genode's source code follows certain time-tested conventions regarding the
|
||||
coding style and code pattern, which are important to us. The coding style
|
||||
is described in the following document:
|
||||
|
||||
:[http://genode.org/documentation/developer-resources/coding_style]:
|
||||
:[https://genode.org/documentation/developer-resources/coding_style]:
|
||||
Coding Style Guidelines
|
||||
|
||||
We know from experience that for new developers, adhering the coding style can
|
||||
|
||||
Reference in New Issue
Block a user