commit | e35bc4e2c7632bfffda71cce53ac23722f92f33e | [log] [tgz] |
---|---|---|
author | Mike Voydanoff <voydanoff@google.com> | Tue Jun 12 15:53:02 2018 -0700 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Jun 13 03:27:35 2018 +0000 |
tree | a5bfb682e43bbe83afb582167d767c08009afde8 | |
parent | 7026740ee5b6e4bb420234c8f4132086455325e4 [diff] |
[ddk][nand] Add NAND class and partition GUID fields to nand_info_t struct The NAND class is used to determine which driver should bind to the NAND device: - NAND_CLASS_PARTMAP binds NAND partition map driver - NAND_CLASS_FTL binds FTL driver - NAND_CLASS_BBS binds NAND bad block skip driver The GUID field contains the partition type GUID from the NAND partition map. Change-Id: I48280ef100afbed20537559449a3dfa5d8d15c0e
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.