From 770c4e4629ee2c16421916239ac3a1be6a9ad176 Mon Sep 17 00:00:00 2001 From: "Eric S. Raymond" Date: Sat, 1 Oct 2011 19:56:22 -0400 Subject: Clean more Berlios URls off web pages and docs. --- .gitignore | 1 + NEWS | 4 +- README | 2 +- gps.xml | 4 +- gpsd_json.xml | 4 +- srec.xml | 4 +- www/README | 5 +- www/future.html | 8 -- www/hardware-head.html | 186 ---------------------------------------------- www/hardware-head.html.in | 184 +++++++++++++++++++++++++++++++++++++++++++++ www/history.html | 9 ++- www/index.html.in | 5 -- www/references.html | 48 +----------- www/upstream-bugs.html | 45 ----------- 14 files changed, 201 insertions(+), 308 deletions(-) delete mode 100644 www/hardware-head.html create mode 100644 www/hardware-head.html.in diff --git a/.gitignore b/.gitignore index 1154ca0a..17f7f5e5 100644 --- a/.gitignore +++ b/.gitignore @@ -105,6 +105,7 @@ www/gpspipe.html www/gpsprof.html www/hacking.html www/hardware.html +www/hardware-head.html www/index.html www/installation.html www/libgps.html diff --git a/NEWS b/NEWS index 5ee2c2cf..46068dd0 100644 --- a/NEWS +++ b/NEWS @@ -185,7 +185,7 @@ and returns, 'rtcm104v2' rather than 'rtcm104'; this is design forward for when RTCM104v3 is fully working. -* Sun Feb 17 2008 Chris Kuethe - 2.37 +* Sun Feb 17 2008 Chris Kuethe - 2.37 The C++ bindings, Garmin USB support, and multiple instances of ntp pps thread starting were fixed. Handling of odd PPS signals was improved. The eye candy in the PHP visualizers was fixed. @@ -263,7 +263,7 @@ * Wed Jul 6 2005 Eric S. Raymond - 2.28-1 The 2.27 source tarball somehow got truncated on upload. - Due to procedural mechanics at berlios.de, shipping a new release + Due to procedural mechanics at Berlios, shipping a new release seems to be the least painful way to recover. This release is identical to 2.27 except the roadmap stuff has been added to TODO. diff --git a/README b/README index 42bef8fe..d42820a0 100644 --- a/README +++ b/README @@ -96,7 +96,7 @@ included: * Support for multiple devices. * Other test tools -- gpsfake, gpscat, gpsmon. -Chris Kuethe maintains the OpenBSD port, shipped +Chris Kuethe maintains the OpenBSD port, shipped the 2.34 release, is our SiRF and low-level protocols expert, and does a lot of general hacking and support. He has release authority. diff --git a/gps.xml b/gps.xml index f26b2fef..422ca324 100644 --- a/gps.xml +++ b/gps.xml @@ -345,9 +345,7 @@ Chris Kuethe chris.kuethe@gmail.com (gpxlogger), Chen Wei weichen302@aol.com (gegps). -This manual page by Eric S. Raymond esr@thyrsus.com. -There is a project page, with xgps -screenshots, at berlios.de. +This manual page by Eric S. Raymond esr@thyrsus.com diff --git a/gpsd_json.xml b/gpsd_json.xml index ab67003b..e6ba3d3b 100644 --- a/gpsd_json.xml +++ b/gpsd_json.xml @@ -2277,9 +2277,7 @@ the members of the corresponding JSON object type. AUTHOR -The protocol was designed and documented by Eric S. Raymond. It -is maintained by the GPSD -project. +The protocol was designed and documented by Eric S. Raymond. diff --git a/srec.xml b/srec.xml index 85a1b26c..e774a2f8 100644 --- a/srec.xml +++ b/srec.xml @@ -302,9 +302,7 @@ indicating the starting execution address. From an anonymous web page, itself claiming to have been derived from an old Unix manual page. Now maintained by the GPSD -project, which added endianness clarifications. -There is a project page for gpsd here. +project, which added endianness clarifications. diff --git a/www/README b/www/README index c4dd6ac2..313538ab 100644 --- a/www/README +++ b/www/README @@ -1,10 +1,7 @@ -This subdirectory contains the web pages for the berlios.de repository. +This subdirectory contains the project web pages. To upload them after modifying, run "./upload'. You must have xmlto, the docbook DTD (Ver 4.1.2) and asciidoc (Ver 8.5.1+) installed for this to work. -Note: The PDFs on the site are not in the code repository, they'd -just bulk it up. Be careful not to delete them. - diff --git a/www/future.html b/www/future.html index b0ec6110..234b8e1f 100644 --- a/www/future.html +++ b/www/future.html @@ -79,14 +79,6 @@ new protocol.. See that document for our tentative release schedule:

For more on specific tasks planned for upcoming releases, see our TODO file.

-

Changing hosting sites

- -

We're presently (April 2010) hosted at berlios.de, but find that it -has become extremely flaky of late (logins failing due to broken SSL -certs is the most recent symptom). We plan to change sites some time -in 2010.

-

Delegating DBUS support to geoclue

We're going to stop shipping DBUS notifications directly at some point. diff --git a/www/hardware-head.html b/www/hardware-head.html deleted file mode 100644 index 4d1abac2..00000000 --- a/www/hardware-head.html +++ /dev/null @@ -1,186 +0,0 @@ - - - - - - - - Compatible GPSes - - - -

- - -
- -
-
-Search for hardware information here: - - -
- - - - - -
- -Google - - - - -
  - - - - - -
- -Web - - -gpsd.berlios.de -
- - - - - - - - -
-
- -
-
- -

gpsd should work with any GPS or AIS receiver using an -RS232C or USB interface that advertises NMEA-0183 compliance. Here -are some notes on hardware we have tested. Hyperlinks lead to -technical information. The "Works with" column is the last -gpsd version with which this receiver is known to have been -successfully tested; A in this column -means we have a regression test load for the device that is checked -before each release. Vendors are listed in alphabetical order.

- -

There is also a table of PPS-capable -receivers which may be appropriate for timing use.

- -

Warning: the baudrate-hunting code in gpsd -tickles serious firmware bugs on some Bluetooth and USB devices. -These bugs may send affected GPSes catatonic. See this bug warning for a description -of the problem. Where possible, we indicate this in the device table.

- -

Icons used in the table: - -

    -
  • marks devices with Excellent performance: gpsd -recognizes the receiver rapidly and reliably, reports are complete and -correct.
    • - -
  • marks -devices with Good performance: gpsd has minor problems -or lag recognizing the device, but reports are complete and -correct.
    • - -
  • marks devices with -Fair performance: reports have minor dropouts or problems, -including occasional transient nonsense values.
    • - -
  • marks devices with Poor performance: -reports frequently have values that are wrong or nonsense.
    • - -
  • marks devices which are Broken; -gpsd frequently fails to recognize the device at all.
    • - -
  • marks devices that needed the -gpsd -b option when tested. Usually these are Bluetooth -devices with defective firmware that does not handle baud-rate changes -properly. Some poorly-designed USB devices choke if they are fed too -many probe strings; these may work better with recent versions of -gpsd, which interleaves probe writes with the first few -packet reads.
    • - -
  • marks devices for which we have a -regression-test load. These are checked on every release.
    • - -
  • marks devices that have been -discontinued by their manufacturers.
    • - -
  • marks devices which will be recognized by -the Linux hotplug system when they are plugged in. If you installed -gpsd from a binary package,or did "make udev-install" from -the source distribution, this should mean you never have to launch -gpsd manually; the udev syatem will launch it for you when -it sees a device of this kind go active.
    • -

- -

Note that in most cases (including the -bug), poor ratings reflect problems not in gpsd but rather in -device design and firmware so badly botched that gpsd cannot -compensate.

- -

This table is generated from a capability database in the -gpsd source tree. Please help us enrich the database with -new devices by filling out this -form.

- -
 
- - diff --git a/www/hardware-head.html.in b/www/hardware-head.html.in new file mode 100644 index 00000000..f49f3546 --- /dev/null +++ b/www/hardware-head.html.in @@ -0,0 +1,184 @@ + + + + + + + + Compatible GPSes + + + + + + +
+ +
+
+Search for hardware information here: + + +
+ + + + + +
+ +Google + + + + +
  + + + + + +
+ +Web + + +@SITESEARCH@ +
+ + + + + + + + +
+
+ +
+
+ +

gpsd should work with any GPS or AIS receiver using an +RS232C or USB interface that advertises NMEA-0183 compliance. Here +are some notes on hardware we have tested. Hyperlinks lead to +technical information. The "Works with" column is the last +gpsd version with which this receiver is known to have been +successfully tested; A in this column +means we have a regression test load for the device that is checked +before each release. Vendors are listed in alphabetical order.

+ +

There is also a table of PPS-capable +receivers which may be appropriate for timing use.

+ +

Warning: the baudrate-hunting code in gpsd +tickles serious firmware bugs on some Bluetooth and USB devices. +These bugs may send affected GPSes catatonic. See this bug warning for a description +of the problem. Where possible, we indicate this in the device table.

+ +

Icons used in the table: + +

    +
  • marks devices with Excellent performance: gpsd +recognizes the receiver rapidly and reliably, reports are complete and +correct.
    • + +
  • marks +devices with Good performance: gpsd has minor problems +or lag recognizing the device, but reports are complete and +correct.
    • + +
  • marks devices with +Fair performance: reports have minor dropouts or problems, +including occasional transient nonsense values.
    • + +
  • marks devices with Poor performance: +reports frequently have values that are wrong or nonsense.
    • + +
  • marks devices which are Broken; +gpsd frequently fails to recognize the device at all.
    • + +
  • marks devices that needed the +gpsd -b option when tested. Usually these are Bluetooth +devices with defective firmware that does not handle baud-rate changes +properly. Some poorly-designed USB devices choke if they are fed too +many probe strings; these may work better with recent versions of +gpsd, which interleaves probe writes with the first few +packet reads.
    • + +
  • marks devices for which we have a +regression-test load. These are checked on every release.
    • + +
  • marks devices that have been +discontinued by their manufacturers.
    • + +
  • marks devices which will be recognized by +the Linux hotplug system when they are plugged in. If you installed +gpsd from a binary package,or did "make udev-install" from +the source distribution, this should mean you never have to launch +gpsd manually; the udev syatem will launch it for you when +it sees a device of this kind go active.
    • +

+ +

Note that in most cases (including the +bug), poor ratings reflect problems not in gpsd but rather in +device design and firmware so badly botched that gpsd cannot +compensate.

+ +

This table is generated from a capability database in the +gpsd source tree. Please help us enrich the database with +new devices by filling out this form.

+ +
 
+ + diff --git a/www/history.html b/www/history.html index f2fe17fb..9f4912f4 100644 --- a/www/history.html +++ b/www/history.html @@ -124,7 +124,7 @@ remote-procedure-call-like way (e.g., without having to worry about gpsd's protocol or how to unpack its data into a C structure).

Eric's work became the prototype for gpsd-2.0. In mid-August of -2004, Eric moved the project to berlios.de with the approval and +2004, Eric moved the project to Berlios with the approval and cooperation of all three of the 1.x maintainers. (The main reason for that choice of hosting site was that it was among the first to offer Subversion, which was new technology at the time and which @@ -170,7 +170,12 @@ marine AIS receivers and pass it to clients.

href="http://thedailywtf.com/Articles/Bad-Code-Offsets-Open-Web-Innovation.asp">won the first Good Code Grant from the Alliance for Code Excellence.

-

In March 2010 the project moved from Subversion to git.

+

In March 2010 the project changed version-control systems, moving +from Subversion to git. In April 2011, it changed build systems, +dumped autotools for scons.

+ +

In late September 2011, the announcement that the Berlios forge site +would be shutting down at the end of 2011 forced the project to move.

Further forks of gpsd seem unlikely, as the project is now sufficiently large and visible to co-opt most developers who might diff --git a/www/index.html.in b/www/index.html.in index 0c55e684..63863561 100644 --- a/www/index.html.in +++ b/www/index.html.in @@ -209,11 +209,6 @@ href="@DOWNLOAD@">Releases

Browse Code
Developer access to master git repository
-
Debian mirror
-
Debian mirror, updated every 7 minutes.
- -

If you are using a Debian-based distribution (including Ubuntu) you can probably install gpsd through your regular package manager or by typing "sudo apt-get gpsd" at the command diff --git a/www/references.html b/www/references.html index 21525d7d..7e594629 100644 --- a/www/references.html +++ b/www/references.html @@ -307,7 +307,7 @@ href="vendor-docs/garmin/garmin-binary.pdf">December 1999 version here; comparing them may be useful. Supported by gpsd. -

Garmin Simple +
Garmin Simple Text Protocol
Some digital cameras are alleged to use this very simple textual report format.
@@ -476,51 +476,7 @@ Formulary
-
-
-Search for more information here: - - -
- - - - - -
- -Google - - - - -
  - - - - - -
- -Web - - -gpsd.berlios.de -
- - - - - - - - -
-
- -
-
-
+ diff --git a/www/upstream-bugs.html b/www/upstream-bugs.html index adb318e8..ccd14339 100644 --- a/www/upstream-bugs.html +++ b/www/upstream-bugs.html @@ -333,51 +333,6 @@ canonical places. This was filed as a bug with Apple and is reported fixed.

-

 

- -
-Search for GPS-related information here: - -
- - - - - - - - - - - -
Google
  - - - - - - - -
Web gpsd.berlios.de -
- -
-
- -
-- cgit v1.2.1