> By the way, I was wondering how the device node changes from ttyACMx to > ttyACM(x+1) without the tty_hangup() call - and I notice that removing > this call makes no difference - the device node remains the same. I'd have to look at the innards of the code but if the existing tty is still in use (has a reference count) then the re-registration of the device will get a new device identifier. The hangup makes sure the tty is seen to have gone away. In the case where you know the hardware was removed so the port was unregistered and re-registered then the hangup only matters to ensure user space knows. I'd guess in your case that the time taken for "hangup, tasks exiting, cleanup.." is slower than the time for the re-registration to occur so the port hasn't been cleaned up in time to be re-allocated. Alan -- 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
