misc/66547: Palm Tungsten T USB does not initialize correctly
Espen Tagestad
>Number: 66547
>Category: misc
>Synopsis: Palm Tungsten T USB does not initialize correctly
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Tue May 11 12:50:13 PDT 2004
>Closed-Date:
>Last-Modified:
>Originator: Espen Tagestad
>Release: 4.10-PRERELEASE
>Organization:
>Environment:
FreeBSD terminator.killer.no 4.10-PRERELEASE FreeBSD 4.10-PRERELEASE #6: Tue May 11 21:19:56 CEST 2004 esp...@terminator.killer.no:/usr/obj/usr/src/sys/TERMINATOR i386
>Description:
Palm Tungsten T USB fails to initialize witht the uvisor/ucom driver. Kernel is configured with device uvisor and device ucom. When pressing the hotsync-button on the cradle, connected to one of the USB-ports, the following is written out on the console:
ucom0: Palm, Inc. Palm Handheld, rev 1.10/1.00, addr 3
ucom0: Palm, Inc. Palm Handheld, rev 1.10/1.00, addr 3
(Yes, to identical lines.)
Then, after about 2-3 seconds, this error message follows:
ucom0: init failed, TIMEOUT
device_probe_and_attach: ucom0 attach returned 6
uhub0: port 2, set config at addr 3 failed
uhub0: device problem, disabling port 2
I guess the device should be connected to ucom0, or ugen0. I can't find any good documentation on how to do this but I suppose that device should come up as ucom0, which then could be used from pilot-link, or some of the other sync utilities.
>How-To-Repeat:
Press the hotsync button.
>Fix:
Have no idea.
>Release-Note:
>Audit-Trail:
>Unformatted:
_______________________________________________
freebs...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs...@freebsd.org"