Fuchsia 2024 roadmap overview

    • Fast and reliable workflows for engineers using Rust in the platform source tree: CI for rust-analyzer, <5s check cycles, discoverable Fuchsia Rust API documentation, and streamlined process to keep third-party Rust libraries up to date.

    • Support for CPU Profiling across all supported architectures, improve Fuchsia tracing for developers.

    • SDK can be used to bring-up new hardware. This includes developing a board driver, drivers for peripheral devices on the board, and implementing board definitions for the hardware using the SDK.

    • Enable all DFv2/FIDL drivers to be built, tested, and debugged with the SDK and Bazel, as part of the platform source tree or in their own standalone repository.

    • FIDL element deprecations can be treated as compile-time warnings, improving awareness of platform evolutions.

    • Google Test (aka gtest) is the preferred, support unit test framework for driver authoring in the Fuchsia platform source tree and with the SDK (replacing zxtest for the same purpose).

    • Enable Driver Conformance tests to be distributed and run by driver authors, to validate that their driver conforms to published interfaces before publishing back to Fuchsia.

    • Fuchsia to start providing a stable driver application binary interface (ABI) for at least six months for downstream products that use drivers compiled through the SDK. This confirms the platform's commitment to delivering reliable and long-lasting driver support.

    • Framework and APIs for system power management.

    • Bluetooth LE Audio, MAP profiles, OBEX profiles and HFP Handsfree.

    • Starnix is running on RISC-V ISA on an emulator.

    • Starnix support for accessing various hardware subsystems through sysfs.

    • Unified address space support for faster syscalls.

    • Support eBPF (Extended Berkeley Packet Filter) in Starnix..

    • Full strace and ptrace support in Starnix.

    • Support SELinux process access control in Starnix.

    • Support for running driver conformance tests against all partner and platform product configurations, validating any related drivers against built system images.

    • All actively developed and net new drivers are migrated to, and built on, DFv2 and FIDL.