| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* A small correction for the sample C code in libgps.xml.
* Lots of web page ToC menu fixups: duplicates removed, missing entries
added, spelling fixed, etc. Also, all the entries are in the same
order, so they don't "jump around" when you move from one page to
another.
* To move things closer to [X]HTML standards compliance, I added an
alt="" to many of the small gpsd logos at the top of the menu.
* The ohloh.net stuff at the top of the page is now four table data
entries in one row of a table. It extends off to the right on many
displays, which is ugly. If you expand your browser to see all of it,
you end up with long lines of text, which are hard to read. I broke
the table into two rows of two table data entries each.
Signed-off-by: Eric S. Raymond <esr@thyrsus.com>
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Fixed some errors in the capability database.
|
| | |
|
| | |
|
| |
|
|
| |
...and revert our changes at deactivation time.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Update the web page and the welcome to vendors with the new stuff
about IRC channels and PHP status pages. Clean up the site-update
machinery. Add build-time dependencies on xsltproc and python to the
spec file.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
One of the longest-lived bugs bites the dust. Axiom Sandpiper II is now
tested and working. David Mandala's bug turned out to be a consequence of
two unrelated problems: (1) The Sandpiper doesn't respond to a normal
SiRF probe, and (2) SiRFs echo anything unknown you send at them, so you
get false positives if the positive respone is the same as the probe string.
We're archiving the documentation here because it's only findable one place
on the web (at <http://www.allsurplus.net/Axiom/>), and that location looks
unstable when the surplus store's supply runs out.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
* Note that we encourage free reuse too, not just redistribution.
* Some OEM kits are just boards, EVKs usually to have nice cases, full
documentation, proper power supplies and test software.
* We may describe a chip/protocol/system in a human-friendly document, not
just in the source somewhere.
* Clarify that we try for broad operating system support by inviting fans of
various UNIX-ish environments. I know we have a couple of OSX users on-list.
|
| |
|
