> That is if you don't make USB mistake 3245: The OsciPrime mistake, where > your product uses a generic VID:PID. The end result, at least in sigrok, > is needing to give the driver a full USB path.
Well, if your device makes such a mistake, then you will hit problems sooner or later with one approach or another. I believe that the UDEV rule file syntax allows you to specify the device's serial number too, so that may be enough to tell the devices apart. > That is USB mistake #1175: not-portable hardware. On the contrary, a device that presents itself as a serial port should work on Windows (with a minimal .INF file), on MacOS and so on, without the need for special drivers or additional USB libraries. A virtual serial port can also be easier to manage. You can pipe and filter things to and from it using standard OS tools. The old Bus Pirate, for example, had a serial port and newer ones have USB, and that's transparent for the software clients. Serial ports can be tunneled to and from computers with standard tools. Any software written for a humble serial port can be easily ported and reused on different devices. Each microcontroller has different USB libraries, but there is always an easy USB CDC example to copy-and-paste that gets you a virtual serial port in no time. Of course, a taylor-made USB protocol can be faster and generally better, but the standard USB virtual serial port paradigm is well known, well tested and has the advantages listed above too. Regards, rdiez ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ sigrok-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sigrok-devel
