On Fri, Apr 07, 2000, Dunlap, Randy <[EMAIL PROTECTED]> wrote:
> With uhci, I didn't get any kind of error messages printed.
> uhci elapsed time for 1000 video capture frames: 1 min:07 sec.
> I ran camstream + cpia + uhci for a few minutes and camstream
> seemed to hang up. I can't Close (via window mgr) it or kill it
> (via kill -9). Repeated one more time. I can't tell if this
> is a uhci problem or a camstream problem. Johannes, if you
> want me to look further at this, how would you suggest that
> I do it? I do have a CATC $$$ analyzer.
I've run into the same problem. I'm going to debug it soon. Since I can
reproduce it here, I don't think I'll need any traces from you for now.
> For the cpia camera, I removed external hub #5 (Ark) and
> connected the cpia camera to a kbd/hub (bus-powered).
> This made the hub driver unhappy (lots of "port 2 over-current
> change") messages, so I also removed self-powered hub #4
> (Aspire kbd/hub). After this, I could connect the camera and
> detect it without errors.
> As Johannes pointed out a few days ago, to really be USB compliant,
> the USB software needs to detect and prevent device connections
> that are this deep in the topology, but that's low priority IMO.
We should probably be more worried about power budgeting instead of hub
nesting depth. Although I think the latter will be easier to implement
:)
JE
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
