commit | c7d0cc75bdbaed03ce5e66c906167775e27834ea | [log] [tgz] |
---|---|---|
author | Mike Voydanoff <voydanoff@google.com> | Sun Oct 21 10:36:03 2018 -0700 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Oct 23 03:52:18 2018 +0000 |
tree | 89f1ec83c4aa2a6fd32effaea8909f90f279efaf | |
parent | cd72f61e618927f69b2b8f15ef5de6acc623fdbc [diff] |
[build] Add support for custom device trees Currently all arm64 targets that use the boot shim use a common dummy device tree binary. But the bootloaders for some Qualcomm boards require a custom device tree binary with msm-id and board-id matching the board. So here was add optional feature for board specific device tree binaries. TEST: Builds, boots in arm64 qemu Change-Id: I5e7b960edf90b627fb4272a86d811b6d4b10bf17
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.