• Protocol through which board drivers can create composite node specs.
  • Error codes for the CompositeNodeManager protocol.
  • Represents a bind rule condition.
  • The type of Fuchsia package that a driver component is inside of. More details about the various package categories are available at:
  • Protocol through which a parent node controls one of its children.
  • Error codes for the Node protocol.
  • Protocol through which a driver manages a node that it is bound to. Drivers should maintain their client connection to the node. Dropping the client connection while the driver is running will cause the driver framework to remove the driver and node from the topology. If the driver has set host_restart_on_crash to “true” in their component manifest, dropping the connection will initiate a restart of the driver host and driver.



Type Aliases§