Thanks for the info... a couple questions:
Greg KH <[EMAIL PROTECTED]> writes:
> Since the device is a vendor specific one, you can either sniff the
> protocol by using an analyzer (a physical one, or one of the windows
> ones that have been mentioned on this list) and determine what is
> needed to be sent to the device in what order to get it to work. This
> is what I had to do to get the HandSpring Visor to work. Only after I
> got it barely running did HandSpring release the specs for the device
> (although this was probably more due to the time it takes dealing with
> a company instead of any other reason.)
I slogged through the list archive (and that for usb-devel) and
haven't found a reference to the winblows utility in question... do
you have a pointer handy? How difficult is it to get the necessary
information this way?
> Or try contacting Palm to get the specs on the device.
Well, I'm trying this route since if they say 'yes' it's a lot less
work on my part ;-) but unfortunately, their developer webpages never
seem to be up when i go there.
> If you do either of the above, let me know and either make up a patch, or
> give me the information and I'll add it to the module.
I'd really appreciate that, since I have no clue about anything USB.
ian
--
----
Ian Soboroff [EMAIL PROTECTED]
University of MD Baltimore County http://www.cs.umbc.edu/~ian
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
