name: rzv-ai-applications
description: |
This snap contains selected AI applications from renesas-rz/rzv_ai_sdk, built for RZ/V2H.
The DRP-AI TVM runtime is staged from renesas-rz/rzv_drp-ai_tvm, v2.5.1.
snapcraft: https://github.com/canonical/rzv_ai_applications/blob/main/snap/snapcraft.yaml
slots:
drp-ai-slot:
interface: custom-device
custom-device: drp-ai-device
devices:
- /dev/drpai0
- /dev/drp1
- /dev/udmabuf
- /dev/rgnmm
- /dev/rgnmmbuf
plugs:
gpu-2404:
interface: content
target: $SNAP/gpu-2404
default-provider: mesa-2404
drp-ai-plug:
interface: custom-device
custom-device: drp-ai-device
This snap is used to run AI application demos of our (Canonical) customer (Renesas) on their RZ/V2H board. The snap requires custom-device interface (“drp-ai-device”) to be able to access these devices:
/dev/drpai0: control node for the DRP-AI accelerator.
/dev/drpai1: control node for the DRP-AI accelerator for codec and opencv accelerator.
In alignment with the mirroring sdk-collections request, this is a +1 from me for granting the requested custom-device usage for the rzv-ai-applications snap.
Given the snap’s functionality and the reasoning provided, this is also a +1 from my side, for
the use of the custom-device interface.
One small clarification before we proceed: your snapcraft.yaml lists /dev/drp1 in the slot’s devices, but your description above refers to /dev/drpai1 (“control node for the DRP-AI accelerator for codec and opencv accelerator”). Could you confirm which device node is correct so the declaration matches the actual hardware?
My sincere apologies for the delay on this request. +2 votes for, 0 votes against, granting use of interface custom-device as defined to snap rzv-ai-applications. This is now live.
Please let me know if you experience any more issues uploading revisions.