Bring hardware into OAL without coupling it to the GUI.

ABI v2 model

A native driver publishes stable driver identity, device enumeration, typed capabilities, health and invoke/cancel behaviour through the OAL driver ABI. Camera drivers publish frames through the native frame callback path instead of embedding large images in JSON.

Start here

• include/oal/driver_api.h — C ABI surface.
• schemas/driver-manifest-v2.schema.json — manifest schema.
• docs/NATIVE_DRIVER_SDK.md — lifecycle, discovery, capabilities and examples.
• drivers/reference_simulated/ — reference implementation.

Driver rules

Keep device-specific protocol/SDK code inside the driver; expose capabilities rather than vendor-name assumptions; support cancellation where the hardware permits; report health/failure clearly; do not make a driver own scheduler/autofocus policy that belongs to Core.

Qualification

The public conformance/certification suite is still OAL 1.0 work. Until then, third-party drivers should pin against a known ABI/development checkpoint and include simulator/build/HIL evidence appropriate to the hardware.

Canonical Native Driver SDK · driver_api.h · manifest schema