commit | ab9394f897d839ce16103baacf9a3be70d45d513 | [log] [tgz] |
---|---|---|
author | Suraj Malhotra <surajmalhotra@google.com> | Fri Jan 11 16:15:09 2019 -0800 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Jan 16 20:04:59 2019 +0000 |
tree | 2537b51f75c0b42a8560698beca30cc4dc21b853 | |
parent | 9cdd6e4f7af185699ff9d0e60899ee35663b6a86 [diff] |
[usb-request] Add private storage support Added a template parameter to usb::Request and usb::UnownedRequest to allow additional private storage for a driver. An unfortunately side-effect of this is that a template parameter needs to be specified when no additional private storage is required (I don't think default template parameters play well with CRTP). Tested: `runtests -t usb-unittest` Change-Id: I46ee50f8904992ecf466d71552abcf6292146758
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.