| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Most drivers now have a control_send method that takes a
payload. provides whatever checksuming and leader/trailer bytes are
needed, and ships it to a specified active device.
This change should not alter any behavior. All regression tests pass.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
It's all conditioned out by #ifdef OCEANSERVER. Some if the
probe logic still needs to be written.
|
| |
|
|
|
|
|
|
|
|
| |
...and copying ascii strings around when they're not going to be printed.
This saves quite a lot of CPU. I processed a 50MB ubx binary file. With
no "-D" options, this saved nearly 2.2M calls to gpsd_hexdump and the
processing time for this file went from 84 seconds to 35 seconds.
|
| |
|
| |
|
| |
|
|
|
|
| |
Now to actually test it...
|
| |
|
| |
|
|
|
|
|
| |
This is without checksum support, and the daemon code does not do
anything with the RTCM data yet.
|
| |
|
|
|
|
|
|
|
|
|
| |
We have a better way in -current: ldattach on the real device, and
relay the data through a pty. ldattach will set up the timestamping
line discipline (there are at least 4 different settings that could be
used) and the relay data out a pty. This is fast - about 60usec. Yay
for the removal of non-portable code that isn't core the purpose of
gpsd. All regression tests pass on openbsd...
|
| |
|
| |
|
|
|
|
|
| |
Change to 'type_name' so gpsd pieces can be used with C++. Reported
by Matt Roberds <mattroberds@cox.net>.
|
| |
|
| |
|
|
|
|
|
|
| |
- actively probe/wake-up ashtech receivers by sending $PASHQ,RID
- parse $PASHR,RID to make device type more informative:
"Ashtech" becomes "Ashtech AC12 ver BQ04"
|
| |
|
|
|
|
|
|
|
| |
>From my balcony the skyview sucks, but the swimming pool and beach view
is real nice. ;)
GPSD,I=Ashtech,O=RMC 1198185318.000 0.005 20.629390 -87.068077 33.03 20.80 20.80 150.3000 0.000 0.000 ? 41.60 ? 3
|
| |
|
|
|
|
| |
Revised the table on the hardware page to reflect user reports.
|
| |
|
|
|
|
|
|
|
| |
Note that the implementation is now somewhat different. Before, this
flag prevented low-level writes to the device. Now it prevents operations
that could *cause* low-level writes -- notably subtype probes, mode
changes, and baud-rate changes.
|
|
|
|
| |
avoid writing when device_readonly is set
|
| |
|
| |
|
| |
|
|
|
|
|
| |
It's unlikely to ever be compiled, but it may be useful reference
material for the itrax3 protocol.
|
|
|
|
|
|
|
| |
now, all itrax features (including italk and $PFST) shall be
controlled with enable-itrax.
obviously i'm hacking on italk again, so make the italk driver compile again.
|
|
|
|
| |
functional but committed to allow for in-tree development.
|
|
|
|
| |
...(notably the TSIP ones). There's a conflict...
|
|
|
|
| |
All regression tests pass.
|
|
|
|
|
|
|
| |
...so the packet sniffer no longer needs to take an argument that is
an rtcm structure. This is a step towards a new and better gpsfake.
No logic or protocol changes. All regression tests pass,
|
|
|
|
| |
Teach the daemon to ignore comment packets led with # and ended with \n.
|
|
|
|
| |
problems created by the last big refactoring patch.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a big, super-intrusive patch but changes no logic at all --
it's all about ripping out some of the gps_device_t structure members
into a new gps_packet_t structure. Even the driver API doesn't change
at all, this is all libgpsd(3) internals being rearranged.
The motivation here is that we want to kill off the ad-hoc Python
implementation of a packet-sniffer in gpsfake. To do that we need to
be able to write a "pure" packet sniffer that uses the same C code as
the daemon's but without being welded to the rest of the libgpsd(3)
code. This is the first step towards that.
|
|
|
|
|
| |
This diff makes that happen, and tries to be forthcoming about
when it is making gpsd run as root.
|
| |
|
|
|
|
|
| |
...we should do the same when setting up the OpenBSD-specific
timestamping code.
|
|
|
|
|
|
| |
Nest appropriately so we can compile on 4.0. Also log correctly so
that users wondering why the sensors don't seem to be working will
have something in their logs.
|
|
|
|
|
|
|
|
|
|
|
|
| |
In recent versions, the kernel keeps timestamps of control line
changes. We also have the nmea(4) line discipline which activates an
in-kernel NMEA parser to extract time information. This is then
exported via the sensors framework for use by openntpd.
This partially worked, but it wasn't until this morning that we had the
control line stuff working.
CK
|
|
|
|
| |
...the same way probe_subtype does, and for the same reason.
|
|
|
|
|
|
| |
The EverMore probe should just flip us into binary mode. Petr gaves me
a heads-up that he's already done this removal in his experimental
sources.
|
| |
|