| commit | a6d76cedc3d5586ceae5bbed648076e34076fa84 | [log] [tgz] |
|---|---|---|
| author | Mike Voydanoff <voydanoff@google.com> | Mon Nov 26 11:11:16 2018 -0800 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Sat Jan 19 04:40:43 2019 +0000 |
| tree | ee0fc5b3023f4de42e0c4fe4e315ce8171b9cc54 | |
| parent | fff702c24919493f3ca779173eaa6306147d9d2a [diff] |
[msm8053] Work in progress on msm8053 support Execution makes it through the boot shim and into the kernel, but mysteriously resets after that. NOTES: Device is flashed via fastboot using scripts/flash-msm8x53-som Power cycling with volume down button pressed gets you into fastboot. Serial debug access is done via special Y-cable that connects to the USB-C port Connect to /dev/ttyUSB0 @ 115200 Finally, if the device fails to boot too many times in a row it will start booting off the boot_b partition (which still contains Linux) instead of boot_a, where Zircon is flashed. to fix that, you can reset the counters by doing: fastboot flash partition kernel/target/arm64/board/msm8x53-som/partition-table.img TEST: attempt to boot on msm8053 hardware as described above Change-Id: I281eb98273952889a85a9e23a8914a7c39f4a2c7
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.