>From the article, it sounds like " udevadm info -a -p
/sys/bus/usb-serial/devices/ttyUSB0/" might be interesting (if it
returns the relevant info)?
Did some digging on FreeBSD, seems it's possible to find the associated
TTY from sysctl:
sysctl -a|grep "^dev\.uftdi"
dev.uftdi.2.%desc: FT232R USB
I think the problem isn't usb device
The problem is serial protocol that don't have a plug and play feature
Em terça-feira, 23 de setembro de 2014, David Torrey
escreveu:
> Does this help? Seems to be a lot more complicated than it should be, but
> at least it’s fairly deterministic.
>
>
> http
Does this help? Seems to be a lot more complicated than it should be, but at
least it’s fairly deterministic.
http://askubuntu.com/questions/184526/how-to-get-bus-and-device-relationship-for-a-dev-ttyusb
Dave
On Sep 23, 2014, at 7:58 PM, Paul Alfille wrote:
> Ok, I'm perplexed!
>
> I need h
We could a automatic search with exceptions
Fir example, instead of telling what device to search (ttys*) tell what
device not to search (tty with ups for example)
Em terça-feira, 23 de setembro de 2014, Paul Alfille
escreveu:
> Ok, I'm perplexed!
>
> I need help mapping device name (e.g. /dev/t
Ok, I'm perplexed!
I need help mapping device name (e.g. /dev/ttyUSB0) to USB bus:devnum that
I get in libusb.
I can probably do it by parsing 'dmesg' but that's rather inelegant.
Perhaps the data is somewhere in /sys or /proc?
The problem is that after searching (and perhaps tuning) USB devices
Hi Paul,
I have another one:
Elabnet (PBM01) -- 0403:6015 -- with UNIQUE product and manufacture ID
Sorry for the delay. I'm still negotiating a sample for your.
Thanks
Dirk
Am 23.09.2014 um 23:27 schrieb Paul Alfille:
> Ok, I did some testing of various USB 1-wire bus masters:
>
> LinkUSB --
On 9/23/14 23:27 , Paul Alfille wrote:
Ok, I did some testing of various USB 1-wire bus masters:
LinkUSB -- 0403:6001 -- FTDI but no identifying charcteristics (Except
serial number, but that's probably not consecutive)
Yeah, standard FTDI vid/pid. Identical to both my LinkUSB and a random
FT
Ok, I did some testing of various USB 1-wire bus masters:
LinkUSB -- 0403:6001 -- FTDI but no identifying charcteristics (Except
serial number, but that's probably not consecutive)
TAI603B -- 10c4:ea60 -- CP210x Unclear if it's generic or not
USB9097 --1a86:7523 -- HL-340 Seems generic
ECLO -- 040
I'm all for auto-detection, when it is possible to do so reliably. As
you mentioned in the other reply, randomly poking at stuff is neither
reliable or safe..
So, the question is what we can do to make it as smooth for the user as
possible..
A possibly a new approach, with OS-specific resolvin
Thank you Ekkehard, for your kind words.
To answer your last question first, you could use the "feature request" on
Sourceforge: https://sourceforge.net/p/owfs/feature-requests/ but few
people seem to do it. Most mention it here. What do you have in mind?
I think the problem with serial devices i
10 matches
Mail list logo
