> I just confirmed that removing the TIOCEXCL ioctl call fixes the > issue. This doesn't really resolve the problem though, as devs should > be able to grab exclusive control of the port without rendering it > useless for future use in the same session. Sorry to reply to this thread again so quickly, but I'm seeing more weirdness. After a few open(fd),close(fd) calls on the device it's no longer responsive. There are no problems opening the device anymore, but dmesg gives me stuff like this when I try talking to the device: http://pastebin.com/QY0NntUx Physical reconnection doesn't alleviate this problem (which is odd because physically disconnecting the device turns it off as well). I have to restart linux to use the device again. Regards, -Pris -- 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
