commit | 64879b4d457d767450b260300264fd7e54b25fbb | [log] [tgz] |
---|---|---|
author | Mike Voydanoff <voydanoff@google.com> | Wed Dec 12 07:44:03 2018 -0800 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Thu Dec 13 00:34:55 2018 +0000 |
tree | 604960bbc900414be4622c3dc986e8db04016fe0 | |
parent | 2412875c11116290b41c6f5e8b869dfddf7742b1 [diff] |
[banjo][usb] Move usb_request_t to a banjo library This is preparation for moving the remaining USB protocols to banjo This requires the following garnet change: https://fuchsia-review.googlesource.com/c/garnet/+/233495 TEST: garnet builds on both platforms, USB works on NUC. This can be shared by future banjo libraries for the USB device, function, HCI and DCI protocols. Change-Id: I9e7182b1098a226323418d65cf8727d0dc6db07e
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.