Recent pulseview sources introduced warnings which are frequent yet not necessary (the conditions they warn about are plausible and not harmful). $ pulseview -D -d fx2lafw "Note for device developers: Ignoring device configuration capability 'Continuous sampling' as it is missing GET and/or SET" "Note for device developers: Ignoring device configuration capability 'Trigger matches' as it is missing GET and/or SET" "Note for device developers: Ignoring device configuration capability 'Connection' as it is missing GET and/or SET" "Note for device developers: Ignoring device configuration capability 'Continuous sampling' as it is missing GET and/or SET" "Note for device developers: Ignoring device configuration capability 'Trigger matches' as it is missing GET and/or SET" "Note for device developers: Ignoring device configuration capability 'Connection' as it is missing GET and/or SET" The specific warnings could get suppressed. The capability of supporting --continuous operation needs to be queried but not configured (it's a fixed feature of a device). The list of known trigger match options cannot get modified at runtime, it's a given device and driver feature set. The conn= spec is a scan option, a (found or specified at scan time) connection text can get queried, but is not adjustable during use after scan.
Fixed with d1b479f74c9d1eb61b56cc4980d7328ec50216df, thanks!