Revert "[banjo] Rename all banjo files to match their library name"

This reverts commit fbbabe8e03d9339fed0bb56e81affcec8ee8a0b1.

Reason for revert: <INSERT REASONING HERE>

Original change's description:
> [banjo] Rename all banjo files to match their library name
> 
> This allieviates some pain for the folks working on the zircon GN
> conversion.  The old copies will be removed once references are removed
> from GN.
> 
> Test: Compiled
> Change-Id: I9f130f7710be70e3445e40649bfa06b1794b0b14

TBR=teisenbe@google.com,mcgrathr@google.com,surajmalhotra@google.com

Change-Id: I4dc504bdeebdc95d03ef6dd484f756a128c788a7
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
69 files changed
tree: f0ebcfaa7cc98b604ec2b5de4e853c4aa707cc4b
  1. bootloader/
  2. docs/
  3. kernel/
  4. make/
  5. prebuilt/
  6. public/
  7. scripts/
  8. system/
  9. third_party/
  10. .clang-format
  11. .clang-tidy
  12. .dir-locals.el
  13. .gitignore
  14. .travis.yml
  15. AUTHORS
  16. LICENSE
  17. MAINTAINERS
  18. makefile
  19. navbar.md
  20. PATENTS
  21. README.md
README.md

Zircon

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.