commit | 059f60f2218319f401669fe4722eb72c6abcfd56 | [log] [tgz] |
---|---|---|
author | Ruchira Ravoori <ravoorir@google.com> | Wed Dec 05 17:18:01 2018 -0800 |
committer | Ruchira Ravoori <ravoorir@google.com> | Fri Dec 07 12:24:45 2018 -0800 |
tree | 6d758ff25601965e90fd9c7d7fd34a7d1cad6e42 | |
parent | 38f535d27d195665af436ac3efdcda3ffac452bc [diff] |
[usb_request_t]Remove list_node_t from the struct. With the recent changes to usb stack, each driver in the usb stack has its own list_node_t so as to avoid stamping on other driver's lists. This changeset removes the list_node_t from the public portion as it is no longer needed. Test: fx full-build. fx serve on vim2. - fx serve on pixelbook using a usb network adapter. lsusb. iochk on usb mass storage device. - fx netboot on astro. lsusb. Change-Id: I6c042f351a66315e40065fbeab282099b72c6c3e
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.