| commit | 8c5393659b9bcbac12eb08016b29dd246fdc21a6 | [log] [tgz] |
|---|---|---|
| author | Mike Voydanoff <voydanoff@google.com> | Thu Dec 13 20:30:31 2018 -0800 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Mon Dec 17 20:17:59 2018 +0000 |
| tree | 1e038029a4e516391e73a099d1281a0ee248b793 | |
| parent | 6effe135a4ec69b3ccb389fd1d0b32c9a088753c [diff] |
[banjo][usb] Begin transition to new banjo based USB protocol We are doing a soft transition, so we retain support for the old USB protocol. The USB bus driver now creates two devices for each USB device, one that supports the new protocol and one that supports the old. And we now have two copies of the usb-composite driver, one for each version of the protocol. Similarly we have two copies of the USB protocol support library. This allows us to run with some USB drivers using the old protocol and some using the new protocol simultaneously. After all the USB drivers are switched to the new protocol we can remove support for the old one. In this CL, all USB drivers are still using the old USB protocol. However this has been tested with the usb-hid driver using the new protocol, which will be submitted as a separate CL. TEST: USB works on NUC. Change-Id: Ibfcc475ea6d7bddc5d1f628d355c4a65e84ab7c9
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.