I’d like to request classic confinement for soon to be released xlnx-config snap. xlnx-config will be used to manage boot artifacts for Ubuntu-enabled Xilinx development boards. Users will use xlnx-config to change the bitstream (FPGA programmable logic ), device tree, boot loader, etc. to modify the functionality of the board.
The snap modifies boot assets so the system loads different HW definitions to the FPGA on boot, and for that it needs to access the system partition. That system partition is not easily available for a confined snap.
The snap also provides a content interface slot. This slot provides specific hardware description files that can be read by the consumer snaps. Consumer snaps will be confined snaps that need these description files to be able to talk to the HW defined in the FPGA, and that depend on the HW defined at that point in the platform (cannot be shipped, then, inside these application snaps).
My team has been working closely with @abeato to develop the system architecture needed to support our unique development environment.
Would it be possible to allow this configuration for the xlnx-config snap?