The Linux Kernel
6.1.0
  • A guide to the Kernel Development Process
  • Submitting patches: the essential guide to getting your code into the kernel
  • Code of conduct
  • Kernel Maintainer Handbook
  • All development-process docs
  • Core API Documentation
  • The Linux driver implementer’s API guide
  • Kernel subsystem documentation
  • Locking in the kernel
  • Linux kernel licensing rules
  • How to write kernel documentation
  • Development tools for the kernel
  • Kernel Testing Guide
  • Kernel Hacking Guides
  • Linux Tracing Technologies
  • fault-injection
  • Kernel Livepatching
  • Rust
  • The Linux kernel user’s and administrator’s guide
  • The kernel build system
  • Reporting issues
  • User-space tools
  • The Linux kernel user-space API guide
  • The Linux kernel firmware guide
  • Open Firmware and Devicetree
    • Kernel Devicetree Usage
      • Linux and the Devicetree
      • Open Firmware Devicetree Unittest
      • DeviceTree Kernel API
    • Devicetree Overlays
      • Devicetree Changesets
      • Devicetree Dynamic Resolver Notes
      • Devicetree Overlay Notes
    • Devicetree Bindings
      • Devicetree (DT) ABI
      • DOs and DON’Ts for designing and writing Devicetree bindings
      • Writing Devicetree Bindings in json-schema
      • Submitting Devicetree (DT) binding patches
  • CPU Architectures
  • Unsorted Documentation
  • Translations
The Linux Kernel
  • »
  • Open Firmware and Devicetree
  • View page source

Open Firmware and Devicetree¶

Kernel Devicetree Usage¶

  • Linux and the Devicetree
  • Open Firmware Devicetree Unittest
  • DeviceTree Kernel API

Devicetree Overlays¶

  • Devicetree Changesets
  • Devicetree Dynamic Resolver Notes
  • Devicetree Overlay Notes

Devicetree Bindings¶

  • Devicetree (DT) ABI
  • DOs and DON’Ts for designing and writing Devicetree bindings
  • Writing Devicetree Bindings in json-schema
  • Submitting Devicetree (DT) binding patches
Previous Next

© Copyright The kernel development community.

Built with Sphinx using a theme provided by Read the Docs.