Try to open shmem for 10 seconds.

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

Wait 10 seconds open shmem.

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

Wait for 10 seconds to open shmem, then print messages and exit.

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

Wait 10 seconds to open HAL's shmem, then print message and exit.

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

Wait for 10 seconds to open shmem, then print messages and exit.

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

Try to open shmem for 10 seconds before giving up.

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

wrs_shm_wait is not save, change is needed.
Additionally use wrs-msg for erorr reporting:
--add msg init function
--replace "fprintf(stderr," with pr_error

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

Open and check for data to be available.
This function is intended to replace wrs_shm_wait.

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

--TRACE - solved
--time jump - solved
--items in MIB are filled now

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

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

There was a problem with calculating fan timeout in libwr. Problem occurs when
there was a jump back in time. Since gettimeofday was used, delta for timeout
calculation became negative.
One solution was to use monotonic clock like in main function of HAL, or use
the same timeout calculations as main function. Second solution was chosen
since it is much simpler.

--remove calculation of fan/temperature read timeout in function
  shw_update_fans
--remove function shw_pwm_update_timeout and variable fan_update_timeout from
  libwr/fan.c as not needed anymore
--remove function shw_get_tics from libwr/util.c and libwr/util.h (not needed
  anymore)
--remove SHW_FAN_UPDATETO_DEFAULT from libwr/fan.h (not needed anymore)
--increase PORT_FAN_MS_PERIOD to 250ms (trade-off 200ms of port update and 500ms
  of temperatures update)
--remove increasing t1 in HAL;s main, since t1 was overwritten anyway by t2.

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

Don't overwrite dot-config's source info with ppsi.conf's source info.
If needed for SNMP other files should be used.

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

oldkey and newkey are not used anymore

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

prevent build error

[...]
install -m 644 Kconfig dot-config wrs_release_defconfig /home/awujek/wrs/repo/build/images/wr/etc
install: cannot stat ‘Kconfig’: No such file or directory
install: cannot stat ‘dot-config’: No such file or directory
install: cannot stat ‘wrs_release_defconfig’: No such file or directory
make[1]: *** [install] Error 1
make[1]: Leaving directory `/home/awujek/wrs/repo/wr-switch-sw/userspace/dot-config'
make: *** [install] Error 1
[...]

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

Benoit Rat authored 9 years ago and Grzegorz Daniluk committed 9 years ago

With release v4.2 we only have one valid user (root) to enter the www
configuration.
The "www root" user also shares the passwd with "ssh root" user.

The new Kconfig option allows dowloading ppsi.conf at boot time, from
TFTP or otherwise.  The filename in the URL can include IPADDR and/or
MACADDR, so the same configuration string can be used to set up a
batch of switches with different configurations.

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

This factorized configuration stuff out of wrap_rootfs into a build
target.  It also adds building and installing "conf" so to allow the
following commands in the target (in /wr/etc):

	  make config

	  make oldconfig     (likely after editing dot-config)

	  make defconfig

I'm unable to build menuconfig at this time, because of missing
symbols in the target's libncurses. I hope to fix this when we
bump buildroot up (thanks Adam for that!)

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

Alessandro Rubini authored 9 years ago and Grzegorz Daniluk committed 9 years ago

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

Otherwise "Received SNMP packet(s) from UDP" is written to file everytime the
agent is asked for the information - if we write to ramdisk, RAM becomes full
over the weekend.

Built from commit e38409d

We need it for some copper SFPs, e.g. Cisco MGBT1

We still need them if somebody want to synchronize a regular (non-WR) PTP
device.

José Luis Gutiérrez authored 9 years ago and Alessandro Rubini committed 9 years ago

For security reasons, php user sessions are destroyed after 10 minutes
of inactivity. After this period, users must login again.

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

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

wr_mon must be seriously audited, and turned back to be ptp-based
instead of hw-based (we may have two ptp ports on the same hw port).

Meanwhile, this adds the peer's MAC address and the PTP state for each
port in "up" state, if ptp is running there. It's not perfect, but
I find it  useful.

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

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

The link lenght is most often wrong, because of missing calibration,
coarse approximation of the diffraction ration and a huge integer
division before multiplication.

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
Acked-by: Grzegorz Daniluk <grzegorz.daniluk@cern.ch>

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

This is the sequence of commits, in --reverse order (oldest on top):

   6cdecd8 wr-servo: bugfix for unlikely whole-second offset
   f47f565 wrs-socket: retry getting a tx_timestamp on failure
   d8718e5 wr: trivial: add tracing of the hooks
   de0f017 proto-starndard: invalidate T1 when entering slave mode
   6be7500 proto-standard: call hook->handle_announce for all announce received
   029fbf3 wr: trivial: remove a never-used IPC command
   832bd0d wr-servo: move generation of the state name earlier
   11c199b WR: set system time from WR time
   6ecdf97 wr-servo: run twice as fast

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

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

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

The "pahse tracking: ON" line was confusing.  It's only role is saying
if tracking has been disabled (by wr_mon itlsef, because a user typed
"t").  So the message is now absent unless tracking is forcibly disabled.

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

And force the compiler to complain. It used to be on by default, bah....

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