Commit f7bb769a authored by James Browning's avatar James Browning

remove trailing whitespace

parent 2460ad9d
Pipeline #32914506 passed with stages
in 8 minutes and 34 seconds
......@@ -244,7 +244,7 @@ Full waf documentation is at https://waf.io/
=== Naming conventions ===
Every binary and script we install has an "ntp" prefix on the name
Every binary and script we install has an "ntp" prefix on the name
because namespace pollution is rude. If you write a new tool that you
want us to install, follow this convention.
......@@ -256,7 +256,7 @@ reduce the amount people have to type. Choose tastefully.
We are devotees of the Unix rule that programs should play nicely
with other programs. We like output formats that are simple,
regular, and machine-parseable without ambiguity. The practical
goal to aim at, given our choice of scripting languages,
goal to aim at, given our choice of scripting languages,
is to make writing script wrappers in Python easy.
There is more than one way to arrange this. If you can design a
......@@ -573,7 +573,7 @@ BUG:: Bugs in the code
LOG:: Log switching and debug levels
CLOCK:: Low-level clock manipulation and validation checks & leap-second code
CONFIG:: Configuration parsing and interpretation
INIT:: Daemon setup
INIT:: Daemon setup
SYNC:: Server synchronization
PROTO:: Protocol machine actions
REFCLOCK:: Reference clock and driver actions
......
......@@ -135,7 +135,7 @@ worthwhile would incorporate at least most of the following:
something that runs over HTTPS on the NTS-KE port.
2. Let client and server packets be formatted differently. Achieve
data minimization by just taking unnecessary fields out of client
data minimization by just taking unnecessary fields out of client
packets altogether.
3. Forbid the use of the legacy MAC field, thus fixing the hairiness
......
......@@ -54,7 +54,7 @@ For a one-off test:
is likely to be either something resembling "/etc/init.d/ntp stop" or
"systemctl stop timeservice".
3. Run ./build/ntpd/ntpd plus the command line parameters from above.
3. Run ./build/ntpd/ntpd plus the command line parameters from above.
4. It will daemonize itself and give you back your terminal prompt.
......
......@@ -17,7 +17,7 @@ a higher-level view than individual comments.
=== l_fp, s_fp, u_fp ===
C doesn't have any native fixed-point types, only float types.
C doesn't have any native fixed-point types, only float types.
To do certain time calculations without loss of precision, NTP
home-brews three fixed-point types of its own. Of these, l_fp is the
most common, with 32 bits of precision in both integer and fractional
......@@ -32,7 +32,7 @@ become an l_fp. For most calculations with l_fp it's easier to
envision it as a 64bit integer that represents time with a unit of
2^-32s, slightly short of 233 ps.
When used to represent dates internally an l_fp must be interpreted
When used to represent dates internally an l_fp must be interpreted
relative to the NTP era (the left 32 bits of the integer part of the
NTP date that got cut off). The NTP prime epoch (or epoch 0) is then
an *unsigned* number of seconds since 1900-01-01T00:00:00Z and
......@@ -64,7 +64,7 @@ integral 64-bit type, this was not guaranteed before C99.
Thus to do calendar arithmetic, NTP used to carry a "vint64"
(variant 64-bit int) type that was actually a union with several
different interpretations; the scalar time64_t which is used the same
different interpretations; the scalar time64_t which is used the same
way but implemented as a uint64_t has already replaced this.
This still has some utility because NTP still runs on 32-bit machines
......@@ -117,14 +117,14 @@ ANSI/POSIX standardization.
The NTP code was written well before calls like clock_gettime(2) that
use it were standardized, but as part of its general cleanup NTPsec
has been updated to do all its internal computations at nanosecond
precision or better.
precision or better.
Thus, when you see a struct timeval in the NTPsec code, it's due to
a precision limit imposed by an external interface. One such is in
the code for using the old BSD adjtime(2) call; another is in getting
packet timestamps from the IP layer. Our practice is to convert from
or to nanosecond precision as close to these call sites as possible;
this doesn't pull additional accuracy out of thin air, but it does
this doesn't pull additional accuracy out of thin air, but it does
avoid loss-of-precision bugs due to mixing these structures.
=== struct peer ===
......@@ -224,7 +224,7 @@ has a (non-portable) 'time' member;
There is some confusion abroad about this interface because it has
left a trail of abandoned experiments behind it.
Older BSD systems read the clock using gettimeofday(2)
Older BSD systems read the clock using gettimeofday(2)
(in POSIX but deprecated) and set it using settimeofday(2),
which was never standardized. Neither of these calls are still
used in NTPsec, though the equally ancient BSD adjtime(2) call
......@@ -240,7 +240,7 @@ have not achieved wide use in applications.
Both ntp_gettime(3) and ntp_gettimex(3) can be implemented as wrappers
around ntp_adjtime(2)/adjtimex(2). Thus, on a Linux system, the
library ntp_gettime(3) call could conceivably go through two levels
library ntp_gettime(3) call could conceivably go through two levels
of indirection, being implemented in terms of ntp_adjtime(2) which
is in turn implemented by adjtimex(2).
......@@ -442,9 +442,9 @@ describes how they fit together.
== The pylib/ntp library
The most important structural thing about the python tools is the
layering of the three most important ones - ntpq, ntpdig, and ntpmon.
layering of the three most important ones - ntpq, ntpdig, and ntpmon.
These are front ends to a back-end library of Python service routines that
installs as 'ntp' and lives in the source tree at pylib/.
installs as 'ntp' and lives in the source tree at pylib/.
=== ntpq and ntpmon ===
......@@ -477,7 +477,7 @@ re-used.
=== ntpdig ===
ntpdig also uses the pylib library but doesn't speak Mode 6.
Instead, it builds and interprets time-synchronization packets
Instead, it builds and interprets time-synchronization packets
using some of the same machinery.
=== MRU reporting ===
......
......@@ -58,7 +58,7 @@ Comments:
1) Errors were found in improper use of tm_year within struct tm,
calculations that did not support year 2000 as a leap year
(it truly is, despite any unchanged comments remaining in
(it truly is, despite any unchanged comments remaining in
the NTP source), and some incorrect date calculations, while
not traditional Y2K errors, would break in the year 2000.
......@@ -89,7 +89,7 @@ Non-Y2K Problems Observed:
2) libntp/caltontp.c:
Has logic I believe will fail starting in year 2100 or so.
Left unchanged/untested as it works well beyond basic NTP 2036
Left unchanged/untested as it works well beyond basic NTP 2036
limit checked by check_y2k.c.
If NTP is implemented on 64-bit machines, this should be fixed
......@@ -98,7 +98,7 @@ Non-Y2K Problems Observed:
In particular the '*' '#' character switch no longer occurs...
only '*' is typed.
NOTE: Author (falsely) stated Y2K is NOT a leap year when it
NOTE: Author (falsely) stated Y2K is NOT a leap year when it
really is.
TRUTH: ACTS will go beyond Y2K: it uses FourDigitYear % 100 values
......@@ -111,8 +111,8 @@ Non-Y2K Problems Observed:
Multiply by 256????
Response from PHK:
The entire protocol is binary, the year is a 16 bit quantity
which according to the manual can have the range 1998-2018.
The entire protocol is binary, the year is a 16 bit quantity
which according to the manual can have the range 1998-2018.
............................................................................
The "Non-Y2K Problems Observed" have been fixed.
......@@ -154,7 +154,7 @@ Wed Jul 14 13:57:43 EST 1999
timelord.att.com: stratum 2, offset -0.000094, synch distance 0.06522
timemaster.att.com: stratum 1, offset -0.010803, synch distance 0.03078, refid 'GPS'
[root@timetest ntptrace]# cd -
[root@timetest ntpdate]# date
[root@timetest ntpdate]# date
Wed Mar 1 01:00:03 EST 2000
[root@timetest ntpdate]# ./ntpdate -b timelord.att.com
14 Jul 13:58:10 ntpdate[12525]: step time server 135.16.xxxx.xxxx offset -19911719.766061 sec
......@@ -168,7 +168,7 @@ timemaster.att.com: stratum 1, offset -0.013598, synch distance 0.03116, refid '
Script done on Wed Jul 14 13:58:28 1999
RESULTS OK.
--------------------END OF TEST1--------------------
--------------------END OF TEST1--------------------
### freeware test configuration
......@@ -201,8 +201,8 @@ Some now-irrelevant material has been removed.
AT&T Freeware Year 2000 Certification
This is the "readme" file for the freeware application which has
been certified by AT&T Labs as part of the "Freeware Y2K
This is the "readme" file for the freeware application which has
been certified by AT&T Labs as part of the "Freeware Y2K
Certification Project".
DISCLAIMER
......@@ -228,9 +228,9 @@ DISCLAIMER
LICENSE TO USE
AT&T's intent is to ensure these Y2K patches are freely
available to the public but will not maintain a public web site
for their distribution. Any copyright claims only only apply to
the specific changes made by Y2K to the code. Any original
copyright holders retain rights to unchanged code. Wherever
for their distribution. Any copyright claims only only apply to
the specific changes made by Y2K to the code. Any original
copyright holders retain rights to unchanged code. Wherever
possible patches will be returned to the current owner(s) of the code.
Owners and publishers are free to incorporate appropriate patches,
......@@ -267,8 +267,8 @@ DISCLAIMER
SUPPORT
See http://y2k.labs.att.com/freeware. There will be no ongoing
support for the project. But if you have some very important issue,
See http://y2k.labs.att.com/freeware. There will be no ongoing
support for the project. But if you have some very important issue,
you may email us at: y2k@y2k.labs.att.com
............................................................................
......
......@@ -19,7 +19,7 @@ dd {margin-bottom: .6em}
div.header {text-align: center;
font-style: italic;}
div.footer {text-align: center;
div.footer {text-align: center;
font-size: 60%;}
img.cell {align: left;}
......
......@@ -107,7 +107,7 @@ over the last 16 seconds.
+unit+ 'number'::
The driver unit number, defaulting to 0. Used as a distinguishing
suffix in the driver device name.
suffix in the driver device name.
+time1+ 'time'::
Specifies the time offset calibration factor, in seconds and fraction,
with default 0.0.
......
......@@ -447,7 +447,7 @@ screen width and looks similar to:
+unit+ 'number'::
The driver unit number, defaulting to 0. Used as a distinguishing
suffix in the driver device name.
suffix in the driver device name.
+time1+ _time_ ::
Specifies the time offset calibration factor, in seconds and fraction.
The default value depends on the clock type.
......
......@@ -197,7 +197,7 @@ since the last poll.
+unit+ 'number'::
The driver unit number, defaulting to 0. Used as a distinguishing
suffix in the driver device name.
suffix in the driver device name.
+time1+ 'time'::
Specifies the PPS time offset calibration factor, in seconds and
fraction, with default 0.0.
......
......@@ -85,7 +85,7 @@ your documentation for details.
+unit+ 'number'::
The driver unit number, defaulting to 0. Used as a distinguishing
suffix in the driver device name.
suffix in the driver device name.
+time1+ 'time'::
Specifies the time offset calibration factor, in seconds and fraction,
with default 0.0.
......
......@@ -143,7 +143,7 @@ with the Hayes connection and hang-up commands and result codes.
+unit+ 'number'::
The driver unit number, defaulting to 0. Used as a distinguishing
suffix in the driver device name.
suffix in the driver device name.
+time1+ 'time'::
Specifies the time offset calibration factor, in seconds and fraction,
with default 0.0.
......
......@@ -220,7 +220,7 @@ switched on by sending the following string.
+unit+ 'number'::
The driver unit number, defaulting to 0. Used as a distinguishing
suffix in the driver device name.
suffix in the driver device name.
+time1+ 'time'::
Specifies the PPS time offset calibration factor, in seconds and
fraction, with default 0.0.
......
......@@ -72,7 +72,7 @@ specific receiver in use will be required.
+unit+ 'number'::
The driver unit number, defaulting to 0. Used as a distinguishing
suffix in the driver device name.
suffix in the driver device name.
+time1+ 'time'::
Specifies the time offset calibration factor, in seconds and fraction,
with default 0.0.
......
......@@ -93,7 +93,7 @@ synchronization without needing the Internet at all.
+unit+ 'number'::
The driver unit number, defaulting to 0. Used as a distinguishing
suffix in the driver device name.
suffix in the driver device name.
+time1+ 'time'::
Specifies the time offset calibration factor, in seconds and fraction,
with default 0.0.
......
......@@ -157,7 +157,7 @@ for the specific unit.
+unit+ 'number'::
The driver unit number, defaulting to 0. Used as a distinguishing
suffix in the IPC unit name.
suffix in the IPC unit name.
+time1+ 'time'::
Specifies the time offset calibration factor, in seconds and fraction,
with default 0.0.
......
......@@ -99,7 +99,7 @@ received.
+unit+ 'number'::
The driver unit number, defaulting to 0. Used as a distinguishing
suffix in the driver device name.
suffix in the driver device name.
+time1+ 'time'::
Specifies the PPS time offset calibration factor, in seconds and
fraction, with default 0.0.
......
......@@ -91,7 +91,7 @@ refclock trimble unit 0 subtype 2 time1 0.020
== Initial Setup and Testing for Palisade / Acutime Receivers ==
1. Read the xref:Pal[Palisade / Acutime] notes.
2. Place the GPS receiver outdoors, with a clear view of the sky for best
2. Place the GPS receiver outdoors, with a clear view of the sky for best
results -- these receivers do not work well indoors.
3. Power up and allow the receiver to obtain UTC offset data. This can take
13 to 30 minutes with outdoor placement, or up to a few hours indoors.
......@@ -105,10 +105,10 @@ refclock trimble unit 0 subtype 2 time1 0.020
5. Connect the host to 'Port A'.
6. Configure the serial I/O port and its xref:sym[symbolic link] on the host.
7. Add the refclock to your +ntpd+ xref:cfg[configuration file].
8. Run +ntpd+ with debug level 2 without detaching from the terminal
8. Run +ntpd+ with debug level 2 without detaching from the terminal
(-d -d -n). Note: debug level 1 may also be used; only errors will be
printed to stdout.
9. Check the ntpd xref:log[event log] or stdout for a line similar to
9. Check the ntpd xref:log[event log] or stdout for a line similar to
'TRIMBLE(0) open at /dev/trimble0' to verify that your serial port opened.
10. The driver will print +TSIP_decode+ lines to stdout as it processes
message packets from the receiver. Note: ntpd must be built with debugging
......@@ -123,7 +123,7 @@ refclock trimble unit 0 subtype 2 time1 0.020
xref:f3[+flag3+] is incorrect, and also if the host is connected to Port B.
11. The driver will print a +trimble_poll+ line with a timecode to stdout when
time is successfully transferred.
.. If TSIP_decode lines are seen but trimble_receive never appears:
.. If TSIP_decode lines are seen but trimble_receive never appears:
... TSIP_decode lines with 'Sats: {list of numbers} : Tracking' display the
number of usable satellites after 'Tracking'. At least four must be tracking
if the receiver does not have a valid stored position, but only one is needed
......@@ -134,16 +134,16 @@ refclock trimble unit 0 subtype 2 time1 0.020
== Initial Setup and Testing for Thunderbolt Receivers ==
1. Read the xref:TB[Thunderbolt] notes.
2. Place the GPS antenna outdoors, with a clear view of the sky for best
2. Place the GPS antenna outdoors, with a clear view of the sky for best
results -- Thunderbolt is not very good at tracking weak signals.
3. Power up and allow the receiver to obtain UTC offset data. This can take
13 to 30 minutes with outdoor placement, or up to a few hours indoors.
4. Configure the serial I/O port and its xref:sym[symbolic link] on the host.
5. Add the refclock to your +ntpd+ xref:cfg[configuration file].
6. Run +ntpd+ with debug level 2 without detaching from the terminal
6. Run +ntpd+ with debug level 2 without detaching from the terminal
(-d -d -n). Note: debug level 1 may also be used; only errors will be
printed to stdout.
7. Check the ntpd xref:log[event log] or stdout for a line similar to
7. Check the ntpd xref:log[event log] or stdout for a line similar to
'TRIMBLE(0) open at /dev/trimble0' to verify that your serial port opened.
8. The driver will print +TSIP_decode+ lines to stdout as it processes
message packets from the receiver. Note: ntpd must be built with debugging
......@@ -170,10 +170,10 @@ refclock trimble unit 0 subtype 2 time1 0.020
been powered off for many months.
3. Configure the serial I/O port and its xref:sym[symbolic link] on the host.
4. Add the refclock to your +ntpd+ xref:cfg[configuration file].
5. Run +ntpd+ with debug level 2 without detaching from the terminal
5. Run +ntpd+ with debug level 2 without detaching from the terminal
(-d -d -n). Note: debug level 1 may also be used; only errors will be
printed to stdout.
6. Check the ntpd xref:log[event log] or stdout for a line similar to
6. Check the ntpd xref:log[event log] or stdout for a line similar to
'TRIMBLE(0) open at /dev/trimble0' to verify that your serial port opened.
7. The driver will print +TSIP_decode+ lines to stdout as it processes
message packets from the receiver. Note: ntpd must be built with debugging
......@@ -208,7 +208,7 @@ NTP error messages. Log entries generated by the driver will be of the form:
Thunderbolt.
[[t2]]+time2+ 'time'::
Specifies the holdover duration for Thunderbolt, in seconds, with
Specifies the holdover duration for Thunderbolt, in seconds, with
default 0 (holdover disabled).
+stratum+ 'number'::
......@@ -229,7 +229,7 @@ NTP error messages. Log entries generated by the driver will be of the form:
[[f3]]+flag3 {0 | 1}+::
Specifies the method used for triggering the receiver's hardware event input.
The default of 0 uses the serial port RTS line. Set to 1 to use the serial
The default of 0 uses the serial port RTS line. Set to 1 to use the serial
port's TXD line instead of RTS. Value is ignored when using a Thunderbolt.
+flag4 {0 | 1}+::
......@@ -293,7 +293,7 @@ to the receiver because of the unconnected TXD line, the driver expects the
receiver to be set to its factory default configuration.
If resetting the receiver to defaults is not desired, verify that 'time base'
is set to UTC in 8e-4a. For the Palisade, verify that 8e-0b is 2 or 3 and
is set to UTC in 8e-4a. For the Palisade, verify that 8e-0b is 2 or 3 and
8e-ad is 2 or 3. For the Acutimes, verify that the 8e-a5 packet mask has at
least 'Event 8f-0b on Port A' and 'Event 8f-ad on Port A' enabled.
......@@ -373,7 +373,7 @@ in steps by several microseconds, likely due to the receiver switching between
cell towers.
IMPORTANT: Turn off the receiver's auto-report feature (CTIME=OFF) because the
driver can't distinguish auto-reports from event capture responses. This is
driver can't distinguish auto-reports from event capture responses. This is
mentioned in the receiver manual.
......@@ -411,9 +411,9 @@ ntpd. The receiver automatically decodes the UTC offset data from the +Almanac+
transmitted by GPS satellites. With good antenna placement, Almanac reception
can be expected to take 13 minutes or more after receiver power-up. The driver
will wait for the receiver to report that its UTC offset is valid before
enabling time transfer.
enabling time transfer.
Time transfer during holdover may be enabled by setting xref:t2[time2] to the
Time transfer during holdover may be enabled by setting xref:t2[time2] to the
maximum allowable holdover duration in seconds.
......
......@@ -80,7 +80,7 @@ written as-is to the +clockstats+ file.
+unit+ 'number'::
The driver unit number, defaulting to 0. Used as a distinguishing
suffix in the driver device name.
suffix in the driver device name.
+time1+ 'time'::
Specifies the time offset calibration factor, in seconds and fraction,
to be used for the West satellite, with default 0.0.
......
......@@ -28,7 +28,7 @@ link:refclock.html[Reference Clock Drivers]
+unit+ 'number'::
The driver unit number, defaulting to 0. Used as a distinguishing
suffix in the driver device name.
suffix in the driver device name.
+time1+ 'time'::
Not used by this driver.
+time2+ 'time'::
......
......@@ -190,7 +190,7 @@ the log file.
entries or kilobytes. The default is 4 kilobytes.
+nonvolatile+ 'threshold'::
Specify the _threshold_ in seconds to write the frequency file, with
Specify the _threshold_ in seconds to write the frequency file, with
a default of 1e-7 (0.1 PPM). The frequency file is inspected each hour.
If the difference between the current frequency and the last value
written exceeds the threshold, the file is written, and the +threshold+
......@@ -260,7 +260,7 @@ The variables operate as follows:
The argument becomes the new value for the experimental huff-n'-puff
filter span, which determines the most recent interval the algorithm
will search for a minimum delay. The lower limit is 900 s (15 m),
but a more reasonable value is 7200 (2 hours). There is no default
but a more reasonable value is 7200 (2 hours). There is no default
since the filter is not enabled unless this command is given.
+panic+ _panic_;;
The argument is the panic threshold, normally 1000 s. If set to
......
......@@ -28,7 +28,7 @@ The first two fields show the date (Modified Julian Day) and time
normally shows clock type and unit (but if you are running in strict
Classic compatibility mode it will show the magic clock address in
dotted-quad notation). The final field is the last timecode received from the
clock in decoded ASCII format, where meaningful. For some clock drivers,
clock in decoded ASCII format, where meaningful. For some clock drivers,
a good deal of additional information can be gathered and displayed as
well. See information specific to each clock for further details.
+
......@@ -274,7 +274,7 @@ Note that this command can be sent from the
allowed in this component to prevent filenames referring to
parts outside the filesystem hierarchy denoted by _prefix_.
|__suffix__ |This part is reflects individual elements of a
file set. It is generated according to the type of a file set.
file set. It is generated according to the type of a file set.
|====================================
+
+type+ _typename_;;
......
......@@ -57,8 +57,8 @@ file. +ntp.keys+ is the normal file used in +ntp.conf+.
[[random]]
== Random Seed File ==
All key generation schemes must have means to randomize the
entropy seed used to initialize the internal pseudo-random
All key generation schemes must have means to randomize the
entropy seed used to initialize the internal pseudo-random
number generator used by the library routines.
It is important to understand that entropy must be evolved for each
......@@ -84,7 +84,7 @@ This file is also used to authenticate remote configuration
commands used by the {ntpqman} utility.
Comments may appear in the file and are preceded with the +#+
character.
character.
Following any headers the keys are entered one per line in the
format:
......
......@@ -45,4 +45,4 @@ provide status information, including time to synchronization in seconds.
If you are running Python at a version older than 3.3, the report on time
to synchronization may be thrown off by NTP clock stepping.
//end
//end
=== Reference Clock Support ===
* link:extern.html[External Clock Discipline and the Local Clock Driver]
* link:driver_howto.html[How to Write a Reference Clock Driver]
* link:driver_howto.html[How to Write a Reference Clock Driver]
* link:generic_howto.html[How to build new generic clocks]
* link:refclock.html[Reference Clock Drivers]
......@@ -29,10 +29,10 @@ include::includes/ntp.keys-body.txt[]
== SEE ALSO ==
link:ntp_conf.html[{ntpdconfman}],
link:ntpd.html[{ntpdman}],
link:ntpq.html[{ntpqman}],
link:ntpkeygen.html[{ntpkeygenman}],
link:ntp_conf.html[{ntpdconfman}],
link:ntpd.html[{ntpdman}],
link:ntpq.html[{ntpqman}],
link:ntpkeygen.html[{ntpkeygenman}],
link:ntpdig.html[{ntpdigman}].
include::includes/footer.txt[]
......@@ -49,7 +49,7 @@ support for querying NTP servers. The 'check_ntp_peer' and
The https://github.com/firehol/netdata/wiki[Netdata] monitoring
solution has native support for realtime monitoring of ntpd,
among a vast number of other system metrics.
among a vast number of other system metrics.
'''''
......
......@@ -103,7 +103,7 @@ that should work until 2399.
=== Unix time ===
The basics of Unix time have already been described.
The basics of Unix time have already been described.
32-bit Unix time will roll over at 2038-01-19T03:14:08, beginning its
second era. It will not roll over to zero but rather to the minimum
......
......@@ -2627,7 +2627,7 @@ ctl_getitem(
quiet_until = current_time + 300;
/* The cast on SRCPORT is required to supress a warning on NetBSD 8.0
* http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=53618
*/
*/
msyslog(LOG_WARNING,
"Possible 'ntpdx' exploit from %s#%" PRIu16 " (possibly spoofed)",
socktoa(rmt_addr), (unsigned)SRCPORT(rmt_addr));
......
......@@ -1825,7 +1825,7 @@ oncore_get_timestamp(
instance->pp->hour, instance->pp->minute,
instance->pp->second,
(long) tsp->tv_sec % 60,
(unsigned)Rsm,
(unsigned)Rsm,
0.1*(256*instance->BEHa[53]+instance->BEHa[54]),
/*rsat dop */
instance->BEHa[55], instance->BEHa[56],
......@@ -2716,11 +2716,11 @@ oncore_msg_CaFaIa(
if (buf[2] == 'I') i = i || buf[6];
if (i) {
if (buf[2] == 'I')
oncore_log_f(instance, LOG_ERR,
oncore_log_f(instance, LOG_ERR,
"self test failed: result %02x %02x %02x",
buf[4], buf[5], buf[6]);
else
oncore_log_f(instance, LOG_ERR,
oncore_log_f(instance, LOG_ERR,
"self test failed: result %02x %02x",
buf[4], buf[5]);
......@@ -3372,7 +3372,7 @@ oncore_check_almanac(
instance->count5_set = 1;
}
#ifdef ONCORE_VERBOSE_CHECK_ALMANAC
oncore_log_f(instance, LOG_DEBUG,
oncore_log_f(instance, LOG_DEBUG,
"DEBUG BITS: (%x %x), (%x %x %x), %x %x %x %x %x",
instance->BEHa[129], instance->BEHa[130],
bits1, bits2, bits3,
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment