And now onto the palm pilot with Kpilot

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



I've looked up the Kpilot manual, and I think I have an okay idea of 
what's going on with it.

I'm trying to get it's detection feature to find my Palm Pilot. CentOS 
does seem to be able to recognize it, because if I run lsusb when 
running a hot sync, I get the following:

[root@localhost dev]# lsusb
Bus 001 Device 010: ID 0830:0060 Palm, Inc. Palm Tungsten T / Zire 71

That's encouraging. My Palm Pilot is actually a Tungsten E, not a T, but 
I'm not sure that's a level of detail that matters at this point.

The Kpilot documentation suggest that I look for the palm pilot at 
/dev/ttyUSB0. That didn't work, but I noticed in my /dev/ directory that 
there was also a ttyUSB1. That didn't work either. But then I noticed 
that both were only apparent when I was hot syncing my Palm, so they 
must be connected to it.

Any ideas, then, as to why Kpilot is not acknowledging them as a Palm 
device the way that lsusb does?

Dave


[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]
  Powered by Linux