On Tue, Jun 25, 2013 at 01:16:59PM -0400, raespi wrote: > >How are you accessing the FTDI devices, if not through their ttyUSB > >ports? Your system should also have some persistant device names for > >these ports in the /dev/serial/ directory if you are using udev. I'd > >recommend using them and making sure each of these devices has a unique > >serial number, in order to always know you are talking to the correct > >device. > I'm using libftdi in userspace to communicate with the FTDI devices. Then that library should somehow be unbinding the device from the ttyUSB port, right? I really don't know how that library works, sorry. > I'm also using mdev. One of the other problems I mentioned in the > original email was how both the /dev/ttyUSB0 and /dev/ttyUSB1 > devices dissapeared when the reset happened. That's because the devices disappeared from the bus, that's to be expected. > Is this something udev might fix ?? No, mdev works much the same way that udev works. > AFAIK mdev gets called by the kernel when there's a hotplug event. > Why didn't the kernel notify mdev to generate the new entries in the > /dev directory ?? Because the devices didn't show back up? Or perhaps, because the libftdi library unbound the tty ports from the device, which would cause them to go away in /dev/ because the library is now talking directly to the device, through the /dev/usb/ device nodes instead of through the tty device nodes. But I'm just guessing here... greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
