|author||Yvonne Yip <email@example.com>||Wed Nov 09 15:31:41 2016 -0800|
|committer||Yvonne Yip <firstname.lastname@example.org>||Mon Dec 12 18:12:02 2016 -0800|
[acpisvc] support acpi events Add the acpi_enable_event API. This call creates a port associated with the ACPI handle, and ACPI events are delivered on that handle. There is a limitation to the current implementation. If there are multiple ACPI handles to the same object, acpi_enable_event will only succeed for the first handle that calls the API. Change-Id: I6d7abfcae7aecd61a4ad8c419b159ebb879d836f
Magenta is the core platform that powers the Fuchsia OS. Magenta is composed of a microkernel (source in kernel/...) as well as a small set of userspace services, drivers, and libraries (source in system/...) necessary for the system to boot, talk to hardware, load userspace processes and run them, etc. Fuchsia builds a much larger OS on top of this foundation.
The canonical Magenta Git repository is located at: https://fuchsia.googlesource.com/magenta
A read-only mirror of the code is present at: https://github.com/fuchsia-mirror/magenta
The Magenta Kernel provides syscalls to manage processes, threads, virtual memory, inter-process communication, waiting on object state changes, and locking (via futexes).
Currently there are some temporary syscalls that have been used for early bringup work, which will be going away in the future as the long term syscall API/ABI surface is finalized. The expectation is that there will be 10s, not 100s of syscalls.
Magenta syscalls are generally non-blocking. The wait (one, many, set) family of syscalls, ioport reads, and thread sleep being the notable exceptions.
This page is a non-comprehensive index of the magenta documentation.