Hello!
[Mon, 11 Apr 2005] Robert Lipe wrote:
> If I'm guessing this problem correctly, it only impacts the read of
> waypoints when the alt is unknown, right? That's a known outtage in
Yup.
> The core problem is that GPSBabel has a (bad) concept of "unknown alt"
> and the Garmin protocols have
> 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
Hello!
[Mon, 11 Apr 2005] Robert Lipe wrote:
> If you can report success with the attached patch on Power, i386, and
> amd64, this change is golden in my book and I'll commit it.
amd64, ia32 emulation on an amd64 and ppc32 produce the same -- mostly
correct -- result for r/w/t now. But things li
> 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
>
Hello!
[Mon, 11 Apr 2005] Robert Lipe wrote:
> > It's a Garmin eTrex (B/W) Firmware version 3.60.
>
> It's a "eTrex Vista". "etrex" refers to the whole family and the
> unadorned name "etrex" refers to the little cheapo non-maping unit.
I knew I was missing something... it doesn't say Vista anyw
Hello!
[Mon, 11 Apr 2005] Robert Lipe 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; autho
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
Hello!
This is the released 1.2.5 (as a debian package):
Downloading from garmin does not cause the high CPU load I was
experiencing before but still results in bad data:
999562023526247432192.00
c^P
c^P
Waypoint
Everything succeeds:
(gdb) run
Starting program: /home/rj/work
8 matches
Mail list logo
