commit | 99f75ef17dfe4ca6ae2df107df30feacad83d68c | [log] [tgz] |
---|---|---|
author | Marie Janssen <jamuraa@google.com> | Fri Jan 25 15:46:47 2019 -0800 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Sat Jan 26 00:20:43 2019 +0000 |
tree | 217de9afda527f661ce3407902def7886c98e21b | |
parent | 98968017c432096abfc08cf56c0fb3961ec030c3 [diff] |
[bt][uart] Fix size of acl data buffer The ACL data buffer wasn't large enough to actually contain some data packets now that we can send things other than events along it (A2DP). Increase the buffer size to the max frame size. Bug: BT-701 Test: run bt-a2dp-sink, connect from phone and play music 🎶 Change-Id: I83d1a0bad45e0a22fea1e8b0b324ce4ee9e35958
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.