[jp] Cannot use the program

  • Previous message: [jp] Cannot use the program
  • Next message: [jp] Cannot use the program
  • Christopher Sean Hilton chris at vindaloo.com
    Fri May 30 09:23:51 EDT 2008

     

    On May 30, 2008, at 8:59 AM, David A. Desrosiers wrote:
    
    > On Fri, May 30, 2008 at 8:48 AM, Christopher Sean Hilton
    > <chris at vindaloo.com> wrote:
    >> This is your rosetta stone so to speak. If my assumption is correct
    >> setting up udev will create the /dev/pilot entry that I mentioned on
    >> hotsync initiation at the Palm device.
    >
    > Assuming his udev rules are correctly set up and the version of udev
    > is a working version (there is one distro out there that silently
    > upgraded udev, breaking all "legacy" udev rules without any migration
    > path forward), he should be able to get his Palm device to sync.
    >
    > Also some of the distributions ship with a broken udev rule for Palm
    > devices which points only to the odd-numbered usb endpoints [0135].
    > Just verify that the rule is correct and catches the device endpoint
    > that your specific device uses (there are always 2 for Palm devices),
    > and it should be fine.
    >
    > Last caveat: There is at least 1 known Palm device which _does not_
    > work with libpisock using udev like this, due to the way it seems to
    > try to "mount" itself as a pseudo filesystem when you physically
    > connect it to a cable or cradle (before hitting HotSync); the Palm
    > Lifedrive.
    >
    > Any Palm device that Linux sees straight away when you simply plug it
    > into a cradle or cable will probably not work properly with udev and
    > hence pilot-link/jpilot/etc. I hope the Palm TX is not one of these
    > devices or we're chasing our tails down a dead-end road.
    >
    > There are recent reports of the m130 also not working, but I haven't
    > discounted that the distributions "changed" something there as well.
    > We're working that out on the pilot-link mailing list now.
    
    USB is a pain in the neck. The way it's implemented on the palm is  
    doubly so. Am I correct in assuming that the reason that newer Palms  
    present a device on the USB bus at plug in time rather than hotsync  
    time is to allow them to charge from your computer. E.g. you have to  
    negotiate for power on the USB bus and the only way to do that to  
    present a device the moment the cable is plugged in?
    
    To tell the honest truth. I'm more interested in Bluetooth Sync than  
    USB sync. The interface appears cleaner.
    
    Chris Hilton                                   e: chris|at|vindaloo| 
    dot|com
    ----------------------------------------------------------------------------
                       "The pattern juggler lifts his hand; The orchestra  
    begin.
           As slowly turns the grinding wheel in the court of the crimson  
    king."
                                                -- Ian McDonald / Peter  
    Sinfield
    
    
    
    

     

     

    More information about the jpilot mailing list