commit | 0569dad21dad7562a0040d79b0170e824b2577b1 | [log] [tgz] |
---|---|---|
author | Venkatesh Srinivas <venkateshs@google.com> | Thu Jan 24 23:06:57 2019 +0000 |
committer | Venkatesh Srinivas <venkateshs@google.com> | Fri Jan 25 01:48:43 2019 +0000 |
tree | 63414c021808e1f5500cf400a0d4b67c4d78377c | |
parent | 5747259dc9debd9699902b0f6624a4f64a7bd72e [diff] |
[scsilib] Definitions of INQUIRY, MODE SENSE (6) commands Structure definitions for the INQUIRY and MODE SENSE (6) commands. * INQUIRY is used to get standard product data for all SCSI Targets and Vital Product Data pages (not yet supported). It is used extensively during the SCSI target probe and enumeration phase. * MODE SENSE (6) lets us read SCSI target readonly state and whether/not 'Force Unit Access' is available. ZX-2314 Tested: Built Change-Id: I2e258533e86643758b13710d0864c249a200b3b5
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.