Request for hardware-observe and DBus plug to slot auto-connection

store-requests privileged-interfaces
1
  • name: fpgad
  • description: FPGA utility that manages bitstream[^1] loading and unloading
  • snapcraft: https://github.com/canonical/fpgad/blob/main/snap/snapcraft.yaml
  • upstream: GitHub - canonical/fgpad
  • upstream-relation: maintainer
  • interfaces:
    • <hardware-observe>:
      • request-type: auto-connection
      • reasoning: Needs access to read compatible strings for FPGA hardware in order to automatically determine the correct process to control the device.
    • <cli-dbus> to <daemon-dbus>:
      • request-type: auto-connection
      • reasoning: The FPGAd snap contains a command line tool (CLI) which communicates with the daemon via a system DBus interface. Without this auto-connection, the user must connect the snap to itself during install. We believe the interface must be a system interface because this is the same DBus interface used by provider snaps[^2] to control the underlying FPGA hardware.

[^1] Bitstreams are binary blobs that configures FPGA devices

[^2] FPGAd provides a mechanism for control of the FPGA hardware to devices running Ubuntu Core, and these provider snaps provide the bitstreams[^1], user space drivers and device tree overlays required to utilise that hardware.

2

This request has been added to the queue for review by the @reviewers team.

3

For context about the auto-connection request to dbus interfaces: Request for kernel-firmware-control, fpga and dbus for fpgad snap - #8 by tchavadar

+1 from me for granting fpgad auto-connection to hardware-observe and requested dbus interfaces (#voteFor)

Thanks!

1 Like
4

this fits the functionality of the snap and the user can expect something like this to be auto-connected. +1 for auto-connecting hardware-observe (#voteFor)

1 Like
5

Voting period has ended. This request is approved with 2 votes for and 0 votes against.

6

Request has been granted. This is now live.

1 Like