On Monday 28 March 2005 11:16 am, Alan Stern wrote:
>
> Why would the hub think that? One obvious cause would be the device
> malfunctioning. Another would be the hub malfunctioning. A more likely
> alternative is electrical noise in the cable appearing to be a signal at a
> time when there sh
On Mon, 28 Mar 2005, James Lamanna wrote:
> Earlier I posted about having long delay issues when reading back
> bytes from a FTDI 232BM USB->Serial chip.
> Now, I've noticed that after a long period of time of semi-continual
> use (maybe 8+ hours) I see the following messages in my kernel.log:
>
Earlier I posted about having long delay issues when reading back
bytes from a FTDI 232BM USB->Serial chip.
Now, I've noticed that after a long period of time of semi-continual
use (maybe 8+ hours) I see the following messages in my kernel.log:
Mar 24 23:46:42 displaytest kernel: hub 2-0:1.0: port
