On Donnerstag, 30. August 2018 17:18:02 CEST James Knott wrote:
On 08/30/2018 11:01 AM, Stefan Seyfried wrote:
Most people really would not expect their first plugged in usb-serial device to turn up as "com33:" in wine. One thing I've noticed is that when a USB serial port is used in Linux, it will always have the same ID, no matter which port it's plugged into. With Windows, on the same computer, the COM port number will change with the USB port used. Now that's confusing!
Always the same name is only guranteed as long as you only have one converter. Add a few and some external hub, and it gets almost random. As almost always with USB, manufacturers are to blame here. Most devices have either no serial number, or a fixed one (FTDI clones). So the device itself can not provide a stable identifier*. On Linux, there is a udev rule to make the devices recognizable, i.e. by providing symlinks with a speaking name. These are based on Vendor/Product, serial number, or physical location in the USB tree. Symlinks are generated in /dev/serial/by-{path,id}/ AFAIK, Windows only uses the physical path if the device has no serial number, and even that can be changed IIRC in the registry or the like. Kind regards, Stefan PS: Some device *do* have unique serial numbers factory programmed. For the Silabs cp210x, there is a tool to reprogram the device, so you can at least generate locally unique ids. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org