commit | 924c9032967026e562265d25d71fe631854b2e4f | [log] [tgz] |
---|---|---|
author | Carl Norum <cjn@google.com> | Wed Jan 23 15:24:44 2019 -0800 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Thu Jan 24 18:43:30 2019 +0000 |
tree | d9cdcb7729c54d2cfb2689f44e17f74c02198466 | |
parent | fd140a51e644a5df058269e08a0fd0cfd0b41078 [diff] |
[mt-usb] correctly set up fifo buffers Interleaved IN/OUT transactions were sometimes failing due to a misconfiguration of the FIFO buffers. When double-packet buffering is enabled, the programmed FIFO size should be encoded as the size of only one of those buffers, not both. This change modifies the FIFO configuration; the previous setup was causing buffer overlaps and spurious garbage transmissions as a result. This new setup keeps all of the buffers properly aligned and isolated. Test: paving Change-Id: If0d4a6bb53559d3eb8b3e7200502be7802b79604
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.