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

Re: [coldsync-hackers] Snapshot: Happier Linux



Andrew Arensburger wrote:
> 
>         I've just uploaded yet another snapshot:
> coldsync-2.0.2-20010330.tar.gz . This one fixes the problem that
> syncing a Palm-brand PDA (not a Visor) hardly worked at all.
>         (If you're curious, the problem turned out to be that I hadn't
> read the CMP spec (not even my own comments about it) correctly:
> during the speed negotiation phase, ColdSync gets a chance to send
> back a packet with a flag saying, "I want to change the speed." I
> thought this meant "I want to change the speed to something other than
> what the Palm suggested." It turns out it meant "I want to change the
> speed to something other than 9600 bps." D'oh!)

Aha!  All those flakey linux serial sync speed issues have
dissappeared.  I can now sync at 115200 (explicitly set in .coldsyncrc)
without a problem.  Not sure how it was working before at all if the
Palm was trying to talk at 9600.  Sort of like me talking with my
girlfriend.  Or maybe this is an unrelated fix for Palm-negotiated
speeds only, but in any case, it works much better.

I did run across a strange seg-fault though. I haven't been able to
replicate it, but here's the snippet of the sync:4 debugging I happened
to have one:

### Cleaning up database.
### Database is open. Not resetting sync flags.
Running sync conduits for "".
Trying conduit [generic]...
  This conduit matches. Running "[generic]"
  This is a default conduit. Remembering for later.
Trying conduit /home/jdsmith/palm/conduits/memo-tidbits...
Trying conduit /home/jdsmith/palm/conduits/showtimes...
Running default conduit
"" is not a ROM database, or else I'm not ignoring it.
Error: GenericConduit::FirstSync: Can't open "": 4.
Segmentation fault

I think the key here might be "Database is open", which I haven't seen
on anything else, and I'm not sure why it was called here, and how not
resetting the sync flags could contribute to a null database listing. 
I'll keep my eyes open.

One caveat:  there was at least one conduit run which used an old
version of Coldsync.pm, but the only difference was a very minor one in
testing the %HEADERS for definedness/existence.

Thanks again for the update, and all your good work.

JD

-- 
This message was sent through the coldsync-hackers mailing list.  To remove
yourself from this mailing list, send a message to majordomo@thedotin.net
with the words "unsubscribe coldsync-hackers" in the message body.  For more
information on Coldsync, send mail to coldsync-hackers-owner@thedotin.net.