Signed-off-by: Michel Arruat <michel.arruat@cern.ch>

Merge all stats with individual statistics:
stats: returns all statistics
stats [0/1/2/3/4/5/6/7]: retuns the appropriate statistic
Signed-off-by: Michel Arruat <michel.arruat@cern.ch>

        wr-streamer.c becomes wr-streamers.c
        wrc-diag.c becomes wrpc-diags.c
Signed-off-by: Michel Arruat <michel.arruat@cern.ch>

Signed-off-by: Michel Arruat <michel.arruat@cern.ch>

Signed-off-by: Michel Arruat <michel.arruat@cern.ch>

Signed-off-by: Michel Arruat <michel.arruat@cern.ch>

I regenerated the header because:
- the name of the HDL module changed from transmission to streamers
- I added new register (tx_cfg5)

Signed-off-by: Michel Arruat <michel.arruat@cern.ch>

Signed-off-by: Michel Arruat <michel.arruat@cern.ch>

        This new test program is using ldevmap and lextest because it is
        interactive.
Signed-off-by: Michel Arruat <michel.arruat@cern.ch>

        extets stands for extented test. The aim is to provide a small
        framework to factorize the usual code for interactive program, like
        parsing arguments, running commands, history, provide a small language
        to pipe commands, etc...
Signed-off-by: Michel Arruat <michel.arruat@cern.ch>

Signed-off-by: Michel Arruat <michel.arruat@cern.ch>

        The main objective is to provide a unique API to map a device
        resource whatever the bus.
        Of course for VME devices the implementation is for the time being,
        highly dependant of the PCI/VME_BRIDGE implementation. There is an on
        going initiative at CERN to expose VME device like PCI device resource
        file.
        Currently CERN_VME_BRIDGE is supported, but only activated through
        a condiational compile statement (see Makefile).
Signed-off-by: Michel Arruat <michel.arruat@cern.ch>

        The current commit replaces the vuart library by a devmap library.
        The goal is to provide a common way for test programs to map a PCI or
        VME resource. Of course the VME inplementation is highly dependant of
        the PCI/VME bridge.
        This new library is not specific to wrpc and should be reconsidered in
        respect with UAL project. For the time being it is located here,
        because it serves the purpose of writing test program for wrpc.
Signed-off-by: Michel Arruat <michel.arruat@cern.ch>

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

this is a software part of new (additional) diagnostics for WR PTP Core.
It allows to access diagnostics values through WB registers (e.g. PCI
bus). This is useful for integration of WR with CERN cotrols infrastructure,
such as FESA. It allows the host machine (of SPEC/SVEC/etc) to easily
access information about the health of WR PTP Core.

we had "warning unused.variable", so let's use it
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

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

While we also have atoi, our custom fromdec/fromhex are more similar
to strtol, and thus useful to parse "number.number" or such stuff.

And since I need to pass negative hex numbers in later commits, here
it is.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

It's not very cleaned-up, but may be useful for other developers.

    * tools/build-random/manybuilds

It builds with randomconfig. It remove ppsi configuration so
the wrpc-sw makefile uses a proper one, even if PPSI_FORCE_CONFIG
is false.

It leave around some files: configs and build logs for warning/error
builds, and only the config for good ones. You'll find them
by "git status".

It also avoids re-building and already known good configuration.

    * tools/build-random/unique-error

This filters error builds to only report one per type.

    * tools/build-random/unique-warning

Same for warning-only failures
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

I spits a number of warnings, and we are not simulating snmp anyways.
Better avoiding the warning than fixing

(thanks randconfig)
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Otherwise we get this:

  ppsi/arch-unix/unix-startup.c:35: multiple definition of `main'
  wrc_main_sim.c:193: first defined here

(thanks randconfig)
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

If we select a host build, we'll have the same assert from
ppsi::arch-unix, becauseI added a non-libc assert to ppsi while adding
it to wrpc-sw.  But ppsi doesn't build its own asser for arch-wrpc, so
the only proble is with host builds.

(thanks randconfig)
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This simplifies, in a way.  Otherwise, we'd need to make most
developer options depend on WR_NODE too.

(thanks randconfig)
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Otherwise we have build errors.

   wrc_main.c:172: undefined reference to `uart_init_hw'
   wrc_main.c:172: undefined reference to `uart_read_byte'
   ppsi/arch-wrpc/wrc_ptp_ppsi.c:103: undefined reference to `uart_init_hw'

If we want to make it optional, we can revert this commit
(thanks randconfig)
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This also include a ppsi commit. We must have both at the same time,
because each uses a feature of the other, to link sw-uart at build time.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

We'd miss some symbols in wrs, besides missing the shell

   shell/cmd_diag.c:32:30: error: 'DIAG_RO_BANK' undeclared

(thanks randconfig)
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

We can't run such stuff in the switch:

(thanks randconfig)
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Otherwise, if we have syslog we fail building:

  lib/syslog.c:197:23: error: 'CONFIG_TEMP_HIGH_THRESHOLD' undeclared

(thanks randconfig)
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Keep assert enabled only for devel_build_test_defconfig
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

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