| commit | 8068a823da9af4d70fdc7756501e7e76b80106de | [log] [tgz] |
|---|---|---|
| author | Suraj Malhotra <surajmalhotra@google.com> | Wed Jan 30 17:39:09 2019 -0800 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Thu Jan 31 02:06:00 2019 +0000 |
| tree | a11e03ddb948a1b331e29b9cc3aa89c9e7b4a45b | |
| parent | 553514117b19973c22db25253f8d941a7dbecab6 [diff] |
[pdev] Remove std::optional from GetI2c, GetGpio, and GetClk The inner types all have default constructors and a way to check if they are initialized so it was redundant to wrap them in std::optional. Tested: runtests on vim2 Change-Id: I1d14b4b8d70b8cece6e4fac31ee1b49d1bc0c15b
Zircon is the core platform that powers the Fuchsia OS. Zircon 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 Zircon Git repository is located at: https://fuchsia.googlesource.com/zircon
The Zircon 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 about 100 syscalls.
Zircon syscalls are generally non-blocking. The wait_one, wait_many port_wait and thread sleep being the notable exceptions.
This page is a non-comprehensive index of the zircon documentation.