commit | e9017556680cbbb504137f737a24da80bafaf97c | [log] [tgz] |
---|---|---|
author | Braden Kell <bradenkell@google.com> | Tue Jan 29 15:19:59 2019 -0800 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Jan 30 15:32:45 2019 +0000 |
tree | 2e4973aae698e0e586b45382952a9bb02403502b | |
parent | 5205b2cb42e26ee53e4eac1ccea03ceb247c606c [diff] |
[scripts] Add ramdisk option to package-image.sh Mediatek devices crash in the bootloader when the decompressed kernel is written to the ramdisk region. Add an option to package-image.sh that will prevent a ramdisk from being added to the boot image, and use this option in the Cleo and mt8167s_ref flash scripts. The default behavior has not changed, so other devices shouldn't be affected. ZX-3356 #done Test: mt8167 ref board boots. Test: Ran package-image.sh and inspected the boot image with a hex editor. Change-Id: If084e162d2bfe9b4ad37339c9b4daacc43791861
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.