| commit | a0e93fd75f51315bc9b9526a9cfdff7ff9cbb561 | [log] [tgz] |
|---|---|---|
| author | Ruchira Ravoori <ravoorir@google.com> | Mon Dec 10 14:31:03 2018 -0800 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Dec 11 03:08:05 2018 +0000 |
| tree | e5c5aa84dd5cdc5e12d9ca61f4c8b1bb2b0003bb | |
| parent | 01fdd88640edb996c16af9492b16991cec8688f6 [diff] |
[usb proto] Make complete_cb as a parameter to usb_request_queue Already reviewed at https://fuchsia-review.googlesource.com/c/zircon/+/232612 However, when including that change in integration review test with garnet change, (patches.json), the dry run fails, unable to apply the zircon change.Infra team is also unsure about the reason. I synched to JIRI_HEAD and removed all the associated dependencies, and generated this change with exact same source and the dry run now succeeds. With usb request having private regions for each layer in the stack, the complete callback and their contexts should not be part of the public part of the usb-request. This changeset modifies usb protocol so that the complete_cb and its context are passed in as parameters. Test: Test with garnet change: https://fuchsia-review.googlesource.com/c/garnet/+/232701 pixelbook: fx serve. fx shell. lsusb. iochk on ums device. audio -d 1 tone. Astro: netboot. lsusb. Change-Id: I691ca2ccd8eeca35711d501ac7b23be4d91161dd
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.