commit | bfb991f4f57c922bc2954cd543a5be65815abd34 | [log] [tgz] |
---|---|---|
author | Dustin Green <dustingreen@google.com> | Fri Jun 15 21:09:46 2018 -0700 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Mon Jun 18 22:16:54 2018 +0000 |
tree | d2a1435f7516f5af0eee3c5d473e584d2c8e13cd | |
parent | debee5a462ecd1ef8fc0a319252684401d00216f [diff] |
[Codec] IOCTL def, to create/get CodecFactory This IOCTL will be used to get a CodecFactory FIDL channel established to drivers like amlogic_video_decoder. The IOCTL asks for the client end of a CodecFactory interface - the driver will create the channel and bind to the server end. This change is needed in zircon before corresponding usage in garnet. Tested: built a change in garnet that uses the defined IOCTL name Change-Id: I319ee78df3fc4ffa517f9534b072699ec38b26a6
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.