commit | 9c32a1d0ca10b1ffdf77d20cb878e6cea0f7e92b | [log] [tgz] |
---|---|---|
author | rvargas <rvargas@google.com> | Thu Jun 07 12:21:28 2018 -0700 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Fri Jun 08 22:47:12 2018 +0000 |
tree | e8c5d03a461bc882f8a369baae010fc1c9fea22c | |
parent | 3d97ec83395ae1033f778d8d13abd880dd7677a1 [diff] |
[nand] Update the nand protocol to operate on data and oob. - READ/WRITE_DATA is now called simply READ/WRITE, and can be used to operate on page data, page OOB or both. - Removed ram_nand implementation of READ/WRITE_OOB. - Deprecated READ/WRITE_DATA and READ/WRITE_OOB (The symbols are still present to allow other implementations to work) Change-Id: Ia8c6e23b1dff999e8df00780bcb1111ea947b537
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.