commit | 13ee3dc5e4c46bf127977ad28645c47442ec517d | [log] [tgz] |
---|---|---|
author | Brijen Raval <braval@google.com> | Wed Jan 30 14:47:15 2019 -0800 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Thu Jan 31 21:16:30 2019 +0000 |
tree | 0c9dec46d36f3151089bcf6e712153c490af83d6 | |
parent | c1cc7f094f688b545300957b57065316287c7462 [diff] |
[sherlock][isp] Move ISP code out of MIPI CSI - Moved out existing ISP Init code from MIPI and put it under ISP - Will be adding other initialization stuff in subsequent CLs. Test: Verified all 3 drivers getting loaded on Sherlock Change-Id: Ibc9143e3916c6af5073bcc919b97a18b33b1850d
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.