Re: The new driver(0.12b4) can't reset the wireless device successful ly, too!

Hi,

On Mon, 5 Jan 2004, Zhang Qiang MT-CN wrote:

> Hi,
> First, thank you very much for your answering my question!
> Second, I compiled the 0.12beta4 driver after doing some adjusts for my
> embeded linux 2.4.4;
> When I insmoded the drivers and insert the USB device, following happended.

[syslog shortened:]
> usbdfu.c: dfu_download_block(): buffer=c201dd0c, bytes=0, block=22
> usbdfu.c: STATE_DFU_MANIFEST_SYNC
> usbdfu.c: DFU: Waiting for manifest phase
> usbdfu.c: STATE_DFU_MANIFEST
> at76c503.c: sending REMAP
> at76c503.c: sleeping for 2 seconds
> at76c503.c: wlan%d: state 9 -> 10 (EXTFW_DOWNLOAD)
> at76c503.c: wlan%d: kevent exit flags=x0
> at76c503.c: wlan%d: kevent 11 scheduled
> at76c503.c: wlan%d: kevent entry flags=x800
> at76c503.c: resetting the device
> hub.c: port 1, portstatus 103, change 0, 12 Mb/s

Looks like usb_reset_device() doesn't work or the port status isn't
reported correctly. I miss a line like "portstatus 110 ..." to see the
port reset.

> usb.c: usb_control/bulk_msg: timeout

guess the device remains in the REMAP state, waiting for the USB reset.

> hub.c: USB device not accepting new address (error=-110)
> at76c503.c: update_usb_intf_descr: ENTER
> usb.c: usb_control/bulk_msg: timeout
> ...
> usb.c: usb_control/bulk_msg: timeout
> at76c503.c: unable to get descriptor
> at76c503.c: update_usb_intf_descr: EXIT with -110

Sorry, I never tried kernel 2.4.4. I'd look into the USB hc
driver you use and/or the USB subsys of 2.4.4. Could you try a newer
kernel version?

/Jörg