On Sun, Jun 16, 2002 at 10:03:43PM -0500, JC wrote:
> I've recently acquired a handspring treo 90 and when attempting to sync
> I run into troubles.
>
> First, visor.c required a product id of 0x0100, while the treo 90 has an
> id of 0x200. I added that to the list of IDs recognized by visor.c, but
> ran into another problem. The Treo 90 has an endpoint of type interrupt,
> which visor.c does not permit. (The usbview output is below). The treo
> is a Palm OS 4.1 device (no idea if that is significant or not).
>
> Comments? Ideas? Or am I all wet? Please reply directly as I am not a
> member of the linux-usb-devel mailing list.
Hm, this is the first Palm device that I've seen with a interrupt
endpoint. If you change the code to accept an interrupt endpoint
(change num_interrupt_in: to have a 1) and the number of bulk in and out
endpoints to 1, how well does the driver work? What does the startup
messages say?
thanks,
greg k-h
----------------------------------------------------------------------------
Bringing you mounds of caffeinated joy
>>> http://thinkgeek.com/sf <<<
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
