When testing with newer compilers and newlib, a mismatch surfaced in
the definition of intptr_t, int32_t, uint32_t.  I don't know why the
library header gets picked up.

This patch, though ugly, fixes the problem by using the "ifdef" names
found in lm32-elf/include/sys/_stdint.h (the offending file).
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

If you use CROSS_COMPILE from the environment, the current system will
try to build host code with the lm32 compiler, and the build stops at
the very beginning. This fixes the problem in the most trivial way.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

include/storage.h had int, this file had in32_t and newer compilers
complain about that. So now both are int, which fits better.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

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

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

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

normally the ip is given after lldp has been initialized or is
modified maually

The optional TLV of LLDP has been added, leaving
two of them still as *todo* since there is not hw
support yet for getting info from the wr-core outer world.

LLDP a vendor-neutral link layer protocol used by network devices
for advertising their identity, capabilities, and neighbors.
Implements a transmit-only nodes, the node only transmit periodically
and doesn't process any LLDPUD.

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

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

This introduces "mode abscal", that forces a gm-lookalike mode in the
node, to send sync once per second. See "absolute calibration" document
by Peter Jansweijer from nikhef. The option is Kconfig'd, but on by
default.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Conflicts:
	ppsi

both "sec" and "hwrs->sec" are 64 bits wide: don't forcibly trim
to 31 bit the value being assigned.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This is a logic &, not an aritmetic one. So "&&" not "&".  The change
has no effect, because the two operands are verified to always be 0 or
1, but what we had was conceptually wrong and forced me to verify.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

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