On Mon, 30 Jul 2007 17:29:56 +0200, Lucio Crusca <[EMAIL PROTECTED]> wrote:
> The only solution I've found in such cases is to unplug and replug the > dongle (even a few reboot cycles aren't enough). However that solution is > not acceptable for me, since the systems should run unattended. > Do you know how could I simulate unplug/replug events from software? Or > any other solution that can run unattended? The symptoms you described point to a sequencer lock-up in the device. Your best bet is to change the brand of the dongle to a more reliable one. If you work for a bigger OEM, you may be able to shop around and have vendors interested. Failing that, you can interrupt the power with a hercon relay driven by a GPIO port or serial port's DTR signal. Here's the C program to drive DTR in Linux: http://people.redhat.com/zaitcev/notes/cycle.c It's a last resort technique which served me well in the past. But usually if it comes to that it's time to seek a new place of employment, because obviously you do not have resources in place to see the project through success. -- Pete ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
