Yes, the hotplug (well, actually it's coldplug and udev) creates two USB devices, /dev/tts/USB0 and /dev/tts/USB1. With palm devices, these entries only show up when the palm is actually trying to hotsync, but palm desktop didn't really seem to care. It tried to use GetCommState when the devices showed up. If I run hotsync program without trying to sync, it doesn't complain. The errors only show after I pres the button. I have USB0 symlinked to /dev/pilot, and I am able to sync with this device using pilot-link compatible apps (mainly gnome-pilot.) Oh, and about that crash--does the mailing list archive have a search engine on it?
Thanks a lot, James
On Thu, 2005-07-07 at 22:28 +0200, Uwe Bonnes wrote:
"James" == James Liggett jrliggett@cox.net writes:
James> I'm not using a "real" adapter. I'm using the visor driver that James> is used to sync a USB palm with things like pilot-link. ThisDoes the hotplug mechanisme create some /dev/ttyUSBx when you plug in the device? Or is the USB VID/PID at least know to the linix kernel drivers?
James> driver emulates a serial port in much the same way that a real James> one does, or so I think. I was just pointing out that people have James> similar behavior with real adapters, so I thought it might be James> relevant. The visor driver calls itself a "serial converter", and James> it does add USB entries in my /dev/tts folder like a real adapter James> would. But, my palm cradle is plugged into an acutal USB port. I James> do have access to a real USB to serial adapter though; I'll play James> around with it. And another thing--I'm also looking into that James> WinMM crash that keeps Palm Desktop from running. The problem is James> that the function DRIVER_FindFromHDrvr is failing, returning a James> NULL value, which wine tries to derefrence in MMDRV_Install, and James> boom--wine crashes.Scan the mailing lists. I had another similar problem, Eric pointed me to some problems in my setup.