Hi all, just to summarize, it really was a problem with the firmware of the hub. Turning individual ports off works properly with the original revision which is based on a NEC chip. All subsequent revisions of the D-Link DUBH4E use a chip from Genesys Logic and have a HW issue that prevents individual power control of the ports.
I would like to thank Alan for the help, and for his patience with frustrated newbies :) I still have one remaining question. In my previous mail I said that it is very logical that the parent hub is reset and powered-up when a child hub is not reachable (because the partent's port to which the second hub is connected has been turned-off). This default behavior is causing much problems for us. I.e. some of the devices that we want to power control are attached to the hubs using active cables (i.e. hubs intemself). And this results in repowering of the whole hub when we turn off the power to the feeding port. Is there a way to cleanly modify the hub.c to disable this feature?. Any pointers about the best place such modification can be made? I believe that the code in hub.c should by default check if the inability to communicate with the child (detected by hub_irq) is a result of a explicit action by the user. Can this info be passed to the hub driver in some way, when one is using ioctl to directly communicate with the devices? Best regards, Vlado P.S. I apologize if this is a duplicate posting, I seem to have problems with sending messages to the list. ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
