commit | e1522c61e99b73ff3d5778969d0db1802fb0d906 | [log] [tgz] |
---|---|---|
author | Brijen Raval <braval@google.com> | Wed Jan 16 13:14:41 2019 -0800 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Jan 30 17:27:03 2019 +0000 |
tree | 131cf127667bb4844444b2f31dacb3d44b4c0942 | |
parent | aba9c9c1e713243dacd57dc87e2a01dd453469e4 [diff] |
[sherlock][camera] Add initial ISP driver support - Re-write Camera Driver according to https://docs.google.com/document/d/113kjqX6IN8wyALSyzBBZtZFrt4g6F3Cdi0dCQtYDZIU/edit?usp=sharing - Implement phase 2 - Add ISP protocol dummy driver - Add ISP_IMPL protocol - Remove Camera Sensor FIDL protocol - Remove Camera test which are irrelevant now - Remove IOCTLs Test: "dm dump" shows all 3 drivers loaded Change-Id: Ida8c38b93b8325f9190ff8175061bc9c91a236b3
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.