commit | f31014752720f0b6cfdfd67447f4eaa6a26ed36e | [log] [tgz] |
---|---|---|
author | Mohan Srinivasan <srmohan@srmohan-glaptop.roam.corp.google.com> | Tue Jun 12 03:35:58 2018 -0700 |
committer | Mohan Srinivasan <srmohan@google.com> | Thu Jun 14 18:50:23 2018 +0000 |
tree | 13bba0ead6722bb5ba8ddcbb72642bbab6e886dc | |
parent | 56c05e02e1da2e275834f57de132b210edeaf05f [diff] |
[amlogic][rawnand] Add a TODO: for tuning of the controller delay. It is set to 200us now, but testing different values for delay, a delay as low as 20us works. Don't want to change this right now before testing various combinations of controller/NAND that we need to support. Also, this should be a controller specific parameter, instead of a hardcoded constant that applies to all controllers. Change-Id: Ie20a68814a81c1be5f364aac4b384ee3e77fd81b
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.