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

This is a safe measure before adding UDP support, which adds a socket.
And we have other ongoing net-related activities too, so I'd better
spend 16 bytes now and feel safer.
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>

Trigger start/stop of PTP from wrc_check_link job instead of PTP's job.
This picks ppsi's new master that matches the change.

We need to remove prototype for an unused function, now that the one
in ppsi changed arguments and we'd otherwise get

  error: conflicting types for 'wr_servo_reset'
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>
Signed-off-by: Alessandro Rubini <a.rubini@gsi.de>

Although we love to build-test stuff and discard at link time, as soon
as we move tasks to be sections, we need to avoid building the file of
the task if not configured in.  This means lib/arp.c and lib/ipv4.c.

But, for consistency, avoid building icmp.c and bootp.c as well.
The alternative, which is ifconfig'ing the task itself results in
warnings like "'ipv4_init' defined but not used".
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

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

This allows several functions to be static in the files where they
are defined. See temperature.c for an example.

But mainly, the idea is allowing ease addition of features (likely
Kconfig'd ones) for specific WR users, without any modification to the
main function and other generic code.  This will happen soon for snmp,
for example.

We may push this a little further, by moving all shell stuff into
shell.c, the ptp task within ppsi itself, and so on. But now my time
is over.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Socket matching depended on the order or sockets. With the new ELF
section (next commit) we get the ICMP socket before some UDP ones, so
the code matched IPV4 and the UDP service did not get the data.

Now we give priority to UDP sockets. So this commit
fixes the problem beforehand.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

The threshold and the repeat interval is set by Kconfig.
The temperatures are read using the temperature framework.

Tested in host environment:

   wrc# faketemp 90 80 10
   wrc# faketemp 90 40 20
   wrc# faketemp 20 30 40

   Jan  1 10:32:09 192.168.16.7 Temperature high: \
                                  roof:90.0000 core:80.0000 case:10.0000
   Jan  1 10:33:09 192.168.16.7 Temperature high: \
                                  roof:90.0000 core:40.0000 case:20.0000
   Jan  1 10:33:18 192.168.16.7 Temperature ok: \
                                  roof:20.0000 core:30.0000 case:40.0000
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>

This shortens the rule-set by two rules, making space for pdelay.

By accepting all ports from 0 to 511, we get all of our services,
including snmp that will be tested soon.  This relaxed check will give
us possibly some false positives (then discarded by the CPU) while
still protecting from most of an hostile or just probing  port sweep.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

The configuration is not called *_defconfig, because we can't just
build it in ./MAKEALL -- we need ppsi to be built with a different
configuration, and this is not autodetected yet (but building from a fresh
clone works).
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>

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

This commit is not breaking the current status, but adds the
ability to build on the host, to simulate and (mainly) to help
me hack the networking code in a simpler/faster environment.

Missing features:
	- ptp
	- build in i386 (currently x86-64 is hardwired)

Also, this commit requires a change in ppsi, that I'm not going to
commit now: we must get rid of the main function (most of that
stuff is done win wrc_ptp.c, which we must replicate  in a unix-compatible
way).

This is the ppsi change

   --- a/arch-unix/Makefile
   +++ b/arch-unix/Makefile
   @@ -4,7 +4,7 @@ A := arch-$(ARCH)

    CFLAGS += -Itools

   -OBJ-y += $A/unix-startup.o \
   +OBJ-y += \
           $A/main-loop.o \
           $A/unix-io.o \
           $A/unix-conf.o \

Local changes in this commit:
      - adding CONFIG_HOST_PROCESS and the auto-generated opposites:
      CONFIG_LM32 and CONFIG_EMBEDDED_NODE (LM32 && NODE)

      - make some config option depend on !HOST_PROCESS

      - Makefile: some dependencies on HOST_PROCESS and the opposite

      - */*.mk: some dev and shell objects depend on
      CONFIG_EMBEDDED_NODE instead of CONFIG_WR_NODE (i.e.: both a
      node and an lm32)

      - new host/ subdir where some placeholders are placed

      - no sdb support on the host
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This, again, is preliminary to host builds, and has no effect.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

These changes have no effect at this point, but are the initial steps
introducing host builds. Some changes are minor cleanups, some depend
on CONFIG_HOST_PROCESS which is not defined at this point.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

We have three temperatures, called "roof", "core", "case"
(yess rubi like word same lengt, s/he most love four).

There is a "faketemp" command that can set one two or all of them.
This allows to test negative temperatures in printouts (White Rabbit
in Siberia does it, but we southish can't test easily).

All temperatures are initialized to invalid. Example:

   wrc# faketemp -10 -2.5
   wrc# faketemp
   fff60000 fffd8003 80000000
   wrc# temp
   pcb:84.7500 roof:-10.0000 core:-2.4999 case:INVALID
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This costs anoter 220 bytes in the binary, becuase we now loop among
all temperature providers in order to return data to the caller.

The providers are clustered using an ELF section.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This commit adds data structures, methods and a process to manage
temperature.  Currently the only temperature being read is the onewire
thermometer, so there is no difference with what we had before.
The cost is 1.1 kB in binary size.

Well, there is a difference: only the stat engine was reading
temperature, while now the thermometer is read continuously (every 15
seconds, or another Kconfig-urable interval).  This takes quite some
CPU time (18.5ms per polling loop, but allows any user to read
temperature (using the API we now provide) without re-reading the
onewire bus.

The real aim of this is monitoring a board-specific set of sensors,
as implemented and show in the next commit.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Also, this changes how to mac address is retrieved in patching pfilter
rules. I'd better use format_mac(get_mac) for the verbose message,
so get_mac is also the source for patching the rules.

register and get_mac/set_mac are guaranteed to be in-sync.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

These numbers are only available at build time; there is no run-time
command to change them as yet.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

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

This allows a node built with CONFIG_VLAN to choose at run-time
whether vlans are allowed or not.  We build both pfilter rule-sets,
and according to the active vlan number we write one or the other.

The case "CONFIG_VLAN is not set" is handled by providing default
NULL pointers for beginning and end of the vlan rule-set.

As a side effect, I renamed the files and the functions in
the pfilter-builder.

This is how it works for me, with CONFIG_PFILTER_VERBOSE set,
so you see different rule-set  are used (29 rules vs. 16 rules):

    wrc# vlan set 0
    0 ("0") out of range
    Command "vlan": error -22
    wrc# vlan off
    fixing MAC adress in rule: use 22:33:44:55:66:77
    pfilter rule 00: 4.00000000
    pfilter rule 01: 1.e4466013
    [...]
    pfilter rule 28: 8.00000000
    current vlan: 0 (0x0)
    wrc# ip set 10.0.0.2
    IP-address: 10.0.0.2 (static assignment)

  (and I am now reachable by untagged frames)

    wrc# vlan set 10
    fixing MAC adress in rule: use 22:33:44:55:66:77
    fixing VLAN number in rule: use 10
    pfilter rule 00: 4.00000000
    pfilter rule 01: 1.e4466013
    [...]
    pfilter rule 15: 8.00000000
    current vlan: 10 (0xa)

  (and I am now reachable on vlan 10)
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Conflicts:
	Makefile

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

This allows a run-time change of the active vlan, if CONFIG_VLAN is
active at build time.  The pfilter rules are being rewritten every
time the vlan is changed (and we have one VLAN only for the CPU).

   wrc# vlan set 0
   0 ("0") out of range
   Command "vlan": error -22
   wrc# vlan set pippo
   0 ("pippo") out of range
   Command "vlan": error -22

   wrc# vlan
   current vlan: 10 (0xa)

   wrc# vlan set 20
   current vlan: 20 (0x14)
   wrc# ip set 192.168.20.2
   IP-address: 192.168.20.2 (static assignment)

      (and the node now replies to ping on vlan 20)

   wrc# vlan set 10
   current vlan: 10 (0xa)
   wrc# ip set 192.168.10.2
   IP-address: 192.168.10.2 (static assignment)

      (and the node now replies to ping on vlan 10)
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This includes a wrs fix by Maciej and a change that prevents warning
when bulding with CONFIG_HOST_PROCESS (which is not there yet).  I
prefer to merge this now, so the next commit picks only its own little
change into the ppsi submodule.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

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

This commit adds the possibility to build an init command in the
binary.  It can be useful to install a number of nodes with a special
configuration, without the need to reach the shell and/or eeprom of
each one.

This is useful, for example, to pass syslog configuration
or the (yet to be implemented) definition of multiple vlans for
etherbone and the wr fabric (frame classes 7 and 6 f the packet
filter). Moreover, I personally love to load a master or slave node
for testing without interacting with the node (or changing the flash
over and over).

This commit also makes reading of commands from storage an optional
feature, but only in the advanced/developer options. Thus, you can
build a wrpc that uses the build-time init commands, or the
flash-stored init commands, both or none of them.

Size effects:
     * no effect if you keep the defaults (no build-time init, flash init)
     * +248 bytes (+ the command itself) if you enable build-time init
     * -1696 bytes if you remove flash-based init (discouraged)
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>