GPSBabel never really had widespread issues of this, but there have been
changes to improve SkyTraq code in subsequent years.
If you DO have an affected device that still shows this problem with
development head (or a released version) and you wish to submit it for
analysis, please contact me (ups
The OP doesn't mention what hardware they have, which makes this hard to
say much about, but it looks like it's mixing two different use cases.
For "real" USB Garmins, as opposed to serial Garmins attached via a
USB/Serial adapters, there are basically two different models for using
Garmins with G
> amd64, ia32 emulation on an amd64 and ppc32 produce the same -- mostly
> correct -- result for r/w/t now.
Yay. I've committed this fix to my tree. Thanx.
> But things like still appear (they
> also happen with 1.2.4 on i386): (ele should be zero/undefined)
>
>
> 99956202352624743
> I knew I was missing something... it doesn't say Vista anywhere in/on
> the thing...
Precious. The ones in the US have it right below the product family name.
http://www.garmin.com/products/etrexVista/hi.html
> > and rebuild tell me if it works. I'm not really proposing that as a
>
Robert Jordens wrote:
> Downloading from garmin does not cause the high CPU load I was
I never received a complaint about this, but I'm assuming you're giving
a nod to this change:
revision 1.18
date: 2004/11/01 17:34:28; author: robertl; state: Exp; lines: +1 -1
> Perhaps the correct thing to do is just mark gpsbabel as incompatible
> on arm.
Until someone that's really familiar with Arm and the issues on it is
willing to help tackle it, that may be appropriate.
Only the systems with FP that looke IEEE-ish will have even a fighting
chance.
RJL
--
To
> If my memory is any good, arm, or atleast one of the debian
> arches, does not support floating point on the CPU and it's
> implemented in the kernel.
I remember when systems like that roamed the earth.
> There are several implemtations of this where one is slow but correct
> and an other tha
> > This looks like a timezone problem I fixed in psitrext back in Oct of 03
> > but it might be needed the 'FREEZE_TIME' fix I applied in April of 04.
>
> Hmm, would that have escaped 1.2.4 somehow?
Hmmm. Should be there. Let's knock these down a few at a time.
> > (Apparently this system d
> This was all with the latest version in Debian which is 1.2.4.
I'll encourage you to go with what's in the top of tree. I've been
meaning to spin a release but just haven't found the time.
> However, most things in are also available in things
> like on most systems but not all of them are.
John Goerzen wrote:
> 've received some more information about failures to build gpsbabel.
> Kurt Roeckx provided some helpful data.
It's not entirely clear which version of GPSBabel is in question here.
> What can we do to help you debug the problem?
Can you provide an account on failing sys
10 matches
Mail list logo
