Re: USB kernel / udev issue with Palm Treo 700p

Hi Alan,

On 4 February 2007 at 11:37, Alan Stern wrote:
| On Sat, 3 Feb 2007, Dirk Eddelbuettel wrote:
| 
| > I think you may be right. The behaviour was not that different between the
| > twp variants of 2.6.18 I tried, one with and one without CONFIG_USB_SUSPEND
| > and CONFIG_USB_DEBUG. 
| > 
| > In either case, it works if you do the following exactly as described:
| > 
| > 1)  Prepare the statement to be executed, in my case 
| > 	pilot-xter -p /dev/ttyUSB1 -l
| >     but do not yet press Enter
| > 
| > 2)  On the Palm Treo 700p, launch the HotSync and press the hotsync icon.
| >     Wait until the 'Connecting with the desktop using Cradle/Cable' appears
| > 
| > 3)  Maybe a half-second or second after the text appears, hit Enter in the 
| >     shell prepared in 1). You will greeted with 'Connected' from pilot-xfer.
| > 
| > The last step also works if you hit enter a little too soon leading to 'no
| > device found' type error. Quick command-recall in bash and re-running the
| > command helped.
| > 
| > Each log hence shows the first failed attempt, the successful attempt as well
| > as a last (failed) attempt when pilot-xfer tries to access the PDA that is
| > not expecting a connection.
| > 
| > I hope all this helps. I purged ohci-hcd as suggested, flushed dmesg,
| > and reloaded the module and sent you the logs in a separate email.
| 
| As near as I can tell, this shows that the kernel behaves the same way 
| regardless of CONFIG_USB_SUSPEND, and all the problems seem to be caused 
| either by the Treo itself or by the pilot-xfer program.
| 
| Do you agree?  While there may indeed be issues remaining to be fixed, 
| none of them are directly connected with the kernel.

I honestly do not know. I use two main 'client' programs -- jpilot and
pilot-xfer -- and neither communicates 'well' (in the sense of how being
equivalent to my old Handspring Visor and my Palm Tungsten C, or my wife's
Treo 300) with the Palm 700p.  I do not know the kernel usb stack well enough
to assess who's fault this is -- the usb controller, the visor driver, the
kernel ... .  I just know that my user experience is not anywhere near where
I'd like.

It seems to me that the Palm 700p uses a variant of the communications
protocol.  E.g. one of our older Linux workstations doesn't even recognise
it, yet has worked flawlessly for years with the 700p.  

What's your take?

Thanks, Dirk

-- 
Hell, there are no rules here - we're trying to accomplish something. 
                                                  -- Thomas A. Edison

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel