Print "-dirty" for:
--at91boot
--startup guide
--switch's tools
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

It is good to have in logs when and what version of rtud started.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

It is good to have in logs when and what version of hal started.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Sometimes we want to print message with high priority without indication that
it is error. This is workaround for this problem.
For example report program's version.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Unfortunately this is non compatible change, but hopefully noone use SNMP
so far. Due to changes in ppsi.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

bugfix for commit:
c552ec92 serspace/wrsw_rtud: Don't inform about waiting for HAL for 5 seconds

I forgot "!" at the beginning of condition
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

This commit also fixes the tools that access ppsi's shmem.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This allows, among other things, to see big jumps happening (if we are
slave and the master jumped in time due to user interaction: this is "only"
useful during developement, i.e. it *very* useful during development).
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Make rtud and rtu_stat to be able to start in parallel with hal and ppsi.
(wait for hal in rtud, wait for hal and rtud in stu_stat)
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Since rtud and rtu_stat wait internally for hal and rtud shmem to be available,
there is no need to check that in startup script. For the same reason we can
remove "sleep 4" before calling rtu_stat.

Also there is no need to check whether ppsi binary is available. Such situation
will be reported in different ways.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

rtu_stat has to wait for hal and rtud to be ready.
It waits for hal's shmem and rtud's minipc connection. There is no need to
wait for rtud's shmem since it is initialized before ipc server is available.

Additionally few minor changes in printouts.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

It may take few seconds to start hal, rtud shouln't complain about it during
5 seconds.
Additionally change fprintf into pr_error.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Sometimes it happens at boot that rts_get_state fails. It may be due to race
condition with ppsi or something else. Anyway try again when rts_get_state
fails.
Additionally print message when got timeout from tmo_expired.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

--Move assert_init macro to libwr/wrs-msg.h
--Add printout to assert_init macro to know which function fails.
--Remove assert_init macro duplication from rsw_hal/hal_main.c
--Remove #include <libwr/shw_io.h> from libwr/shw_io.h (no need to include file
from itself)
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>

Also support HAL and PPSI restarts in wr_mon.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Make monit to start from inittab instead of rcS script.
Add config files for:
--dropbear
--lighttpd

We want that monit don't propagate its state over restart. Move monit.stat to
/tmp.
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>

Additionally change startup script to use start-stop-daemon
Note: start-stop-daemon does not create pid file
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

When monit is started from inittab instead of script /etc/init.d/monit.sh
it will be respawned after its crash.
Support stopping/starting monit by /etc/init.d/monit.sh
To stop monit, STOP signal is sent to it. By this, init will not respawn monit,
because it is still present in process' list.
Add disabling monit in dot-config by option CONFIG_MONIT_DISABLE.
When monit is disabled by dot-config, monit.sh will sleep forever, to
satisfy init and prevent respawning
Update dot-config items in user-manual.

Include only *.conf instead of all files from /etc/monit.d/.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Add explicit error messages when problems with downloaded dot-config file.
Messages added in /etc/init.d/dot-config
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

parameters show up as a result of copy-paste error
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Move:
/etc/init.d/[SK]??<name> to /etc/init.d/<name>
Then create symlinks in
/etc/init.d/rcS/[SK]??* to all files that previously were /etc/init.d/[SK]??*
With exception of monit since monit will start soon from init.

Rename all occurences of changed files.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Date was never restored due to wrong filename in /etc/init.d/S70wr_date
Use saved_date instead of update_date
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Update required because otherwise setting of auxclk hangs the switch.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Add wrs_auxclk to start at boot

NOTE: This branch requires new Gateware! wrs_auxclk will hang switch when using
      gateware from last release of switch.

Added init script /etc/init.d/S70wrs_auxclk to start wrs_auxclk with parameters
read from dot-config.

Added parameters to Kconfig:
--WRSAUXCLK_FREQ
--WRSAUXCLK_DUTY
--WRSAUXCLK_CSHIFT
--WRSAUXCLK_SIGDEL
--WRSAUXCLK_PPSHIFT
All above are used as parameters to wrs_auxclk,
which configure external clock clk2

NOTE: This patch requires new Gateware! wrs_auxclk will hang switch when using
gateware from last release of switch.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Now wrs_auxclk returns:
0 on success
1 on fail or not enough parametes provided (help printed)
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Introduce saving time before restart, which is restored after restart.
Aslo report date of last firmware update.

Add reporting of when last update of switch firmware took place via SNMP.
If update date is not known return "0000.00.00-00:00:00"
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Note: Be aware that date of last update may be not accurate.
One reason is that it uses date stored before last restart, so time needed to restart is not taken into account.
Additionally date stored before restart may be not accurate for many reasons like:
--hard restart (last know date was not saved)
--date was never received from ntp nor set manually
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

--add running all /etc/init.d/K* scripts before restart
--add /etc/init.d/K90time_save.sh script to save current date
--set saved date in case date cannot be received from ntp
--update developer manual
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Add reporting via ifconfig:
--rx errors (counter RX PCS Errors from pstats)
--carrier (counter RX Sync Lost from pstats)
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

--remove description of CONFIG_PTP_*
--add description of CONFIG_PTP_PORT_PARAMS and CONFIG_PTP_CUSTOM
--update description of CONFIG_PORTxx_PARAMS, add proto information
--update timing configuration section with proto and role information
--In apply_dot-config description add hyperlink to chapter where dot-config is
  described instead of document itself. It looks like this part was copied from
  developer-manual.
--by changes above remove information that role is not used.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>