Heads up. While tracking down a problem with libftdi not seeing my
clearly attached USB device. I found a potential problem with the way
libusb searches for USB devices under the linux OS. It uses a priority
search starting with an environment variable followed by the
/dev/bus/usb hierarchy and then the /proc/bus/usb hierarchy. On my
particular Debian system it looks like /dev/bus/usb is only partially
populated with devices ( perhaps the ones supported by kernel drivers???
), while /proc/bus/usb contains a dynamic list of all the devices. I
solved the problem by reversing the order of this search ( /proc/bus/usb
first ). Not a problem with libftdi per se...but I wanted to put this
up somewhere in case anyone else was banging their heads over this.
-Robert
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|
