> The very very simple solution to this is to extend the
> HUB_DEBOUNCE_TIMEOUT in hub.c to something extraordinarily long, like
> 1500 instead of the now set 400.
>
> I understand that this is non standard.
> I also understand that the Linux USB development effort tries to keep to
> the standard as close as possible - a quite noble goal.
It is a timeout. We meet the standard if we take longer. We must not wait
less time than the standard prescribes but we can already take longer, khubd
is not real time.
[..]
> I am not subscribed to the USB-devel mailinglist so please CC to my
> email when replying.
Do you have devices which reliably can be made to work with this change?
Regards
Oliver
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
