On Sat, 27 Jan 2007, Dirk Eddelbuettel wrote: > | > I doubt that. I'd say this new-ish (May 2006) model is 'different'. > | > We have two of these Treo 700p (from Sprint) here, and they both > | > behave identically: > | > > | > 1) they fail with current 'default' 2.6.x kernels from Debian testing > | > and Ubuntu edgy (2.6.18 and 2.6.17, respectively) > | > > | > 2) they work with the 2.6.12 kernel on my last Quantian LiveDVD release > | > > | > 3) they work once CONFIG_USB_SUSPEND is undefined > | > > | > 4) they fail with an older 2.4 kernel > | > > | > Both an old Treo 300 and and old Tungsten C work flawlessly, which why > | > we were so surprised to run into these problems with the news Treo > | > 700p. I will gladly test whatever patches you guys have for me to get > | > the 700p support to where the older Palm devices are. > | > | It might help to see a usbmon log for 2.6.18 with CONFIG_USB_SUSPEND on. > | Instructions for usbmon are in the kernel source file > | Documentation/usb/usbmon.txt. Start copying the log before plugging in > | the Treo and keep it going while you try to use the device. > > In a separate mail, please find usbmon-1t.txt, created using the suggested > instruction. The kernel only differed from the stock Debian kernel through > the required setting of CONFIG_DEBUG_FS. > > The funny thing is that I could not trigger the ttyUBS1 / ttyUSB3 > switch. Could the presence of usbmon alter the behaviour (Heisenbug ?)
There were plenty of funny events in the log, just maybe not the event you were expecting. It certainly looks as if the Treo itself decided to disconnect and reconnect a few times. (Or maybe you unplugged it and then plugged it back in a second later -- that would show up the same way in the log.) In fact, it's possible that these problems are caused by bad USB cable connections. They certainly could result in intermittent disconnects. > visor.c is sort-of functional if you are careful: > > i) Type the command, eg 'pilot-xfer -p /dev/ttyUSB1 -l' but don't yet > press return > ii) On the device, select the hotsync app and press the HotSync logo > iii) Wait until the device displays the 'connecting to ...' text > iv) NOW press return on the shell > > That works. Waiting too long before iv) also spoils it. Strange. Is it possible that the changes in behavior you see are caused by changes in visor.c or pilot-xfer rather than by anything in the USB stack? The log does give the impression that the Treo has difficulty with some of the commands it receives. For instance, it died when it received this vendor-specific control-IN command: c2 02 0000 0000 0012. But it died at other times too. Alan Stern ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
