[jp] A possible solution to your sync problem

  • Previous message: [jp] A possible solution to your sync problem
  • Next message: [jp] A possible solution to your sync problem
  • David A. Desrosiers desrod at gnu-designs.com
    Sun May 13 00:54:51 EDT 2007

     

    On Sat, 2007-05-12 at 21:16 -0700, TR wrote:
    > Note that this may be specific to Ubuntu, as replacing the
    > "/dev/ttyUSB1" entry with "usb:" prevents a sync from occurring on my
    > SuSE box. 
    
    Unless its a bug (note: I run Ubuntu here), the two are not
    interchangeable like that. usb: is for libusb synchronozation (i.e. you
    need to blacklist the visor module first), while pointing J-Pilot to any
    device in /dev is going to use the visor module ("regular" usb sync) for
    the Palm TX. 
    
    libusb does not use anything at all in /dev/ to function, while using
    the visor module (ala /dev/ttyUSB*) does. My two README documents cover
    this in great detail: 
    
    http://www.pilot-link.org/README.usb
    http://www.pilot-link.org/README.libusb
    
    
    -- 
    David A. Desrosiers - desrod at gnu-designs.com 
    "There are four boxes to use in the defense of liberty: soap, 
    ballot, jury and ammo. Use in that order. Starting now."
    -------------- next part --------------
    A non-text attachment was scrubbed...
    Name: not available
    Type: application/pgp-signature
    Size: 189 bytes
    Desc: This is a digitally signed message part
    Url : http://lists.jpilot.org/pipermail/jpilot/attachments/20070513/035cfb59/attachment.pgp 
    

     

     

    More information about the jpilot mailing list