Ezload problems.

[Bernd Walter]

On Wed, Mar 30, 2005 at 04:11:27PM +0400, Alexandre Jouravlev wrote:
> >
> >Try setting hw.usb.uhub.debug=20 befor testing.
> >Would be interesting to see why you see a disconnect event,
> >but no connect.
> >
> >
> As I am not skilled usb developer (this is my first usb project ever) I 
> don't understand much in this output.
> Here is the output of debug session from plugging the device to what 
> happens next:
> 
> ugen0: Device (no firmware), rev 1.00/1.00, addr 2
> uhub_intr: sc=0xc288d790
> uhub_explore dev=0xc2af4380 addr=1
> uhub_explore: uhub0 port 1 status 0x0100 0x0000

This is a root hub - things might be different if you use another
host controller type or an external hub between.
Neverthelesse there is a problem to fix somewhere.

> uhub_explore: port=1 !C_CONNECT_STATUS
> uhub_explore: uhub0 port 2 status 0x0100 0x0003
> uhub_explore: C_PORT_ENABLED 0x3
> uhub_explore: status change hub=1 port=2
> uhub_explore: device addr=2 disappeared on port 2
> ugen0: at uhub0 port 2 (addr 2) disconnected
> ugen0: detached
> uhub_explore: port=2 !CURRENT_CONNECT_STATUS
> uhub_intr: sc=0xc288d790
> uhub_explore dev=0xc2af4380 addr=1
> uhub_explore: uhub0 port 1 status 0x0100 0x0000
> uhub_explore: port=1 !C_CONNECT_STATUS
> uhub_explore: uhub0 port 2 status 0x0101 0x0001
> uhub_explore: status change hub=1 port=2
> uhub_intr: sc=0xc288d790
> uhub_explore dev=0xc2af4380 addr=1
> uhub_explore: uhub0 port 1 status 0x0100 0x0010
> uhub_explore: port=1 !C_CONNECT_STATUS
> uhub_explore: uhub0 port 2 status 0x0100 0x0011
> uhub_explore: status change hub=1 port=2
> uhub_explore: port=2 !CURRENT_CONNECT_STATUS
> uhub_intr: sc=0xc288d790

I asume the messages don't have much time in between?

> And next the following repeated at rate about 2 messages per second:
> 
> uhub_intr: sc=0xc288d790
> uhub_explore dev=0xc2af4380 addr=1
> uhub_explore: uhub0 port 1 status 0x0100 0x0010
> uhub_explore: port=1 !C_CONNECT_STATUS
> uhub_explore: uhub0 port 2 status 0x0101 0x0011
> uhub_explore: status change hub=1 port=2

Will have to check the meaning of those states in USB specs.
Looks like we ignore it for whatever reason.

-- 
B.Walter                   BWCT                http://www.bwct.de
bernd at bwct.de                                  info at bwct.de