| commit | 35216a3e6789537c5617c69c55a06440bb5aa65b | [log] [tgz] |
|---|---|---|
| author | Todd Eisenberger <teisenbe@google.com> | Mon Mar 19 14:36:50 2018 -0700 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Mar 20 17:48:50 2018 +0000 |
| tree | 8c23c17827b9f4c9301e6e2775a208e80e2316ca | |
| parent | 642776c7c38e8fbdbee92f5ec95c92e2c6d7da28 [diff] |
[dev][sdhci] switch to BTI Re-landed version of I8a4bc3a508db17458ddd6324841d1d78306ab320 (git 26c25eb8505e136576ac4a319a77540834b380bd), modified only to build clean. I believe this was reverted in the bulk revert 335c3a414e169804eb9050d784af6cebd0f5c77f because it did not build cleanly. Testing on Acer and Paradise showed no issue. Change-Id: I10b96fa1a6e3f95aac71c501339abf89174be811
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
A read-only mirror of the code is present at: https://github.com/fuchsia-mirror/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.