Bug 1666 - usability, accept abbreviated and/or ambiguous connection specs
Summary: usability, accept abbreviated and/or ambiguous connection specs
Alias: None
Product: libsigrok
Classification: Unclassified
Component: Other (show other bugs)
Version: unreleased development snapshot
Hardware: All All
: Normal normal
Target Milestone: ---
Assignee: Nobody
Depends on:
Reported: 2021-02-24 23:35 CET by Gerhard Sittig
Modified: 2021-02-24 23:35 CET (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description Gerhard Sittig 2021-02-24 23:35:03 CET
Filing this against libsigrok though users will perceive this issue from 
either of the applications.

When drivers require or support the conn= spec, the current implementation 
is rather strict and expects a full user provided value which connection to 
use to communicate to the device. Usability could get improved by accepting 
abbreviated serial port specs like ttyACM0 instead of /dev/ttyACM0, as well 
as ambiguous values like ttyUSB when multiple devices are connected to the 
same kind of serial port and all of them should be used.

There may be individual device drivers which support this feature already 
(uni-t dmms come to mind, though not all of them universally). Ideally the 
feature would be common and applicable to a larger set of drivers. Neither 
is this limited to serial ports, could also apply to USB VID/PID specs, or 
BLE address specs, etc.