1A: Yes, this is what regular --link does now
1B: With --linkusb and a serial number. It does not use the serial
driver, but it does use the ow_link layer. See the changes in
(ow_arg|ow_opt|owlib).c.
Eventually it calls ftdi_usb_open_desc(FTDIC(in), vid, pid, NULL,
serial), where vid/pid is static.
I forgot that you are only dealing with linkUSB rather than DS9097U devices
on a usb-serial connection.
You're right, they should all have the same vid/pid and thus be
identifiable.
So we have several possibilities:
1. started as --link=/dev/ttyUSB0
A. We could use it as currently, with no li
Afaik, the LinkUSB is only using a single VID/PID (0403/6001), which is
shared by all FTDI serial adapters. The latency/buffer sizes are
identical on power up as well. As far as I know, I have no way of
knowing if the FTDI USB device is a LinkUSB or a random serial dongle
connected to who-knows-wha
How about imbedding a list of known good vid/pid numbers and including a
command-line switch of "--forceftdi" to let people test others.
Or actually probe for the latency and buffer sizes you mentioned.
I'm not a big fan of command-line switches. They raise the barrier for new
users. I'd rather t
