On Mon, 4 Oct 2004, Til Schubbe wrote:
> * On 04.10. Alan Stern muttered:
>
> > here's a new version updated for 2.6.8.1. Tell me how it works out.
>
> Thanks for the patch. I applied it and rebooted my box.
> When I switch the camera on I get this:
>
> </var/log/kern.log>
> Oct 4 23:13:42 debian kernel: ehci_hcd 0000:00:1d.7: GetStatus port 4
> status 001803 POWER sig=j CSC CONNECT
> Oct 4 23:13:42 debian kernel: hub 4-0:1.0: port 4, status 0501, change
> 0001, 480 Mb/s
> Oct 4 23:13:42 debian kernel: hub 4-0:1.0: debounce: port 4: total 100ms
> stable 100ms status 0x501
> Oct 4 23:13:42 debian kernel: hub 4-0:1.0: port 4 not reset yet, waiting
> 50ms
> Oct 4 23:13:42 debian kernel: ehci_hcd 0000:00:1d.7: port 4 full speed
> --> companion
> Oct 4 23:13:42 debian kernel: ehci_hcd 0000:00:1d.7: GetStatus port 4
> status 003801 POWER OWNER sig=j CONNECT
> Oct 4 23:13:42 debian kernel: uhci_hcd 0000:00:1d.1: wakeup_hc
> Oct 4 23:13:42 debian kernel: uhci_hcd 0000:00:1d.1: port 2 portsc 0083
> Oct 4 23:13:42 debian kernel: hub 2-0:1.0: port 2, status 0101, change
> 0001, 12 Mb/s
> Oct 4 23:13:42 debian kernel: hub 2-0:1.0: debounce: port 2: total 100ms
> stable 100ms status 0x101
> Oct 4 23:13:42 debian kernel: usb 2-2: new full speed USB device using
> address 2
> Oct 4 23:13:43 debian kernel: usb 2-2: device not accepting address 2,
> error -32
> Oct 4 23:13:43 debian kernel: usb 2-2: new full speed USB device using
> address 3
> Oct 4 23:13:43 debian kernel: usb 2-2: device not accepting address 3,
> error -32
> Oct 4 23:13:43 debian kernel: usb 2-2: new full speed USB device using
> address 4
Everything up to here is expected, given that your camera doesn't support
the usual intialization sequence.
> Oct 4 23:13:44 debian kernel: usb 2-2: device descriptor read/8, error
> -90
> Oct 4 23:13:44 debian kernel: usb 2-2: new full speed USB device using
> address 5
> Oct 4 23:13:44 debian kernel: usb 2-2: device descriptor read/8, error
> -90
But then the new sequence fails too. That's strange, considering that it
worked before. Here's an additional patch you can try; it applies on top
of the previous one. It changes the order of the initialization schemes,
trying the Microsoft scheme first. It also prints additional debugging
information in the system log.
Alan Stern
--- 2.6.8.1/drivers/usb/core/hub.c.1 2004-10-05 11:35:02.000000000 -0400
+++ 2.6.8.1/drivers/usb/core/hub.c 2004-10-05 11:37:55.000000000 -0400
@@ -1469,13 +1469,15 @@
continue;
}
memset(buf, 0, 64);
- (void) usb_control_msg(udev,
+ j = usb_control_msg(udev,
/* Address 0 */
(PIPE_CONTROL << 30) | USB_DIR_IN,
USB_REQ_GET_DESCRIPTOR, USB_DIR_IN,
USB_DT_DEVICE << 8, 0,
buf, 64,
HZ * USB_CTRL_GET_TIMEOUT);
+printk(KERN_INFO "Init get-descr: %d, maxpacket %d\n",
+j, buf->bMaxPacketSize0);
udev->descriptor = *buf;
kfree(buf);
@@ -1695,7 +1697,7 @@
}
/* reset and get descriptor */
- status = hub_port_init(hdev, udev, port, (i >= 2));
+ status = hub_port_init(hdev, udev, port, (i < 2));
if (status < 0)
goto loop;
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
