GPS issue final state?

[Andy Green]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Somebody in the thread at some point said:

| Terrain type should be included. I'm thinking we need a wiki page. Does
| one already exist? It should have a column for terrain.
|
| How to avoid being tricked by "lucky satellite positions"? I guess one
| way would be to run the test multiple times. How many times? How long
| apart? Perhaps, as you did, twice, one day apart?

Just take care that an explanation as fuzzy and unprovable as "lucky
satellite positions" doesn't obscure something else going on.

For example, two guys reported WLAN up makes jitter on GPS.  At the
moment, WLAN defaults to being on, although we will change this shortly
because it doesn't make sense anyway.

GPS being affected by SD Card at all already shows we deal with a
"system level issue".

Currently with U-Boot, there is a 50:50 chance of your USB spamming away
at 6MHz with high slew rate, whether connected to anything or not,
although I have a fix for that pending.  This won't help GPS and has
been "invisible", and can explain the next day having "unlucky satellite
positions".

We're not ready for "GPS issue final state" until we chew through more
angles in software and continue to get reports about how we are doing
from actual GPS users.

- -Andy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkiUD+MACgkQOjLpvpq7dMo9VACgg9CWyiNkQDBV2pFbxos9NN1S
sOsAnjCwANtHjTJb1JyM8LJQlSnW0Sfv
=JSnw
-----END PGP SIGNATURE-----