Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Additionally check whether link is down
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

By this when the link is down at startup, link_status is set to LINK_DOWN
in wrc_check_link. It does not go through state LINK_WENT_DOWN.

Due to this bug, despite of link was down one packet was sent by bootp.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

When a number contains "0" on 9th and adjacent lower decimal position
these 0's were not printed.
In practice number:
1000000000 was badly printed as 10
1000000001 was badly printed as 11
1000234567 was badly printed as 1234567
1234567890 was correctly printed as 1234567890
1200000000 was correctly printed as 1200000000

Both stat and gui were affected by this bug.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Mapper didn't work on two machines that I use for testing.
For some reason accessing LM32's memory by 4 bytes solved this problem.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

I re-documented wrpc-dump, because I forgot I already did.
Still, this is a little better than what we had, and it's at the
same leve as SNMP, rather than relegated in an appendix.

So the new docs are committed, and the appendix just lists use of the
tool with old wrpc releases, which is not important to most.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Remove possibility to set ptp into p2p mode when it is not compiled
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

If !CONFIG_SYSLOG, usual verbose output is printed to console.

If CONFIG_SYSLOG, you can send the latency error problems to syslog.
The node sends to syslog only the number of lost frames (FIX THIS)
and the latency if it's more than twice the current running average.
such an average is on 8 samples, so it moves quickly.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Conflicts:
	dump-info.c

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Now the default for configurations that do not select peer-delay
is to not even build peer-delay code. This provides for that, and
adds two configurations for peer-delay operation.

If pdelay is selected, e2e is built as well, but selection is currently
only at build time. This will be fixed later.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Please note that peer delay code is compiled into the ppsi, even if it is
disabled at compile time.
Code is in the binary wrpc, but is never can be reached.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Without this, after the first build of wrpc-sw the ppsi
configuration was never changed.

So if you built e.g. "gsi_defconfig" and then reconfigure
for "gsi_pdelay_defconfig" you'll get no pdelay in there.

For me, and the next maintainers of ppsi, the new configuration option
CONFIG_PPSI_FORCE_CONFIG can be unset in order to test with personale
changes in ppsi configuration.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Also, preserve and restore current configuration, so I don't get mad
when checking with MAKEALL during my tests for new feature.

The rationale for this is that wrpc-sw will soon select different ppsi
choices according to its own configuration, through $(PPSI-CFG-y).
Actually, it already does for the host process build.

MAKEALL must obey this choice, so we trim ppsi configuration
each time we reconfigure wrpc (removing the file would spit an
error instead).

Then, our Makefile forces a ppsi reconfig if ppsi/.config is missing
*or* empty.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>