the WR Switch so that later we can merge.

- this new module contains the PLLs, buffers, PHY and DAC arbiter that
  would be usually copied in the top_level of each design
- it was created to make integration of WRPC in user's design easier and
  cleaner
- it is expected to be extended with more families in which case, only
  the PHY is expected to change
- similar module will be created for Altera

- merged two pkg files (wr_streamers and wr_transmission) into one, i.e.
  a moved the stuff from wr_transmission into wr_streamers and removed
  wr_transmission_pkg.vhd file
- added simulation header in proper place, i.e. ./sim/
- modified build_wb.sh script adapting it to "kind-of convesion" used in wr-cores

- xwr_transmission is a container for rx and tx streamers that might be
  generally useful in non-Btrain projects. it was initially developed
  for Btrain
- it was imported from the following repo/branch/commit
  ssh://git@gitlab.cern.ch:7999/BTrain-TEAM/PS-BTrain-over-WhiteRabbit.git
  ML-addressReviewFeedback
  cfc0fc0eeb1f81f80154a2a30027c1e6df5d0171
- it was imported with history following steps in:
  http://stackoverflow.com/questions/1365541/how-to-move-files-from-one-git-repo-to-another-not-a-clone-preserving-history

Before, the output data would be maintained after to valid_o goes LOW. this causes two problems
- main problem: if there is only single output word, rx_first_p1_o and rx_last_p1_o are
  maintained HIGH, they are generally expected to be pulses
- side problem: the data is maintained - it is OK, but it is supposed to be valid anyway
  only when valid_o is HIGH
So, now the data_o is set to zeros when valid is not HIGH. this should prevent
anyone from relying on the fact that data is maintaned after valid_o goes LOW and
it makes rx_first_p1_o and rx_last_p1_o to be pulses

this is a patch that updates both, the streamers code in wr-cores and
the instantation of streamers. a separate commit just in case that this
is not a good idea.

This is to follow the naming convention and easy coding, if you know that a
signal is a single-cycle pulse, you don't need to worry about edge detection

This is to follow naming convetion for single-cycle pulse signal
This change concern all but the wr_streamers stuff that is in wr-cores.
The change of stuff inside wr-cores will be in the following and
separate commit

This ext_pll_10_to_125m component is part of xilinx platform-dependent
folder. It is used in spec_top entities. Since it was not in the package,
it had to be declared in top files which is not perfect. So, its
declaration was added to the pkg.

t was hard to get fully coherent statistics, especially if they were changing
fast (e.g. 250kHz in btrain). Setting snapshot bit to high copies at the same
instant all the counters to separate registers. as long as snapshot bit is high,
these registers are exposed to WB and SNMP. so one can read it as long as it
takes and the data is still coherent.

Conflicts:

	hdl/rtl/WRtransmission/wr_transmission_wb.vhd
	hdl/rtl/WRtransmission/wr_transmission_wbgen2_pkg.vhd

added tx/rx bfield to the SNMP diagnostics

Conflicts:

	hdl/top/BTrainSPEC/BtrainSpecTop.vhd

it was hard to get fully coherent statistics, especially if they were changing
fast (e.g. 250kHz in btrain). Setting snapshot bit to high copies at the same
instant all the counters to separate registers. as long as snapshot bit is high,
these registers are exposed to WB and SNMP. so one can read it as long as it
takes and the data is still coherent.

this can be useful when reseting remotely and wanting to make statistics. in
such case the SNMP server
1. reads the reset timestamp
2. sets reset high
3. reads the timestamp of the reset
4. sets rest low, new timestamp is done to have exactly the time of start of
   stats

added info about reset to the output registers, as well as the value of the
input register. fixed stats to work with remote reset

domain crossing bugfix in wr streamers stats.

This is to allow in the future to retrieve and reset statistics
collected by WR Streamers via SNMP.

The statistics collected by WR Streamers are passed to WRPC through generic-size
array of 32-bit std_logic_vectors. Such communication is intended to accommodate
communication of WRPC with any user-module that needs to be interface via SNMP

the old rx_lost_o indicates as before two "problems"
1. one or more frames have been lost
2. one or more blocks inside the frame have been lost (probably because
   of CRC error)
However, now we have 3 more outputs:
rx_lost_blocks_o     - indicates only losses of block(s)
rx_lost_frames_o     - indicates only losses of frame(s)
rx_lost_frames_cnt_o - when rx_lost_frames_o=HIGH, indicates how many
                       frames have been lost

in particular:
- moved html files to doc/wb-regs and modified appropriately build scripts
- removed unused wbgen stuff from oldBtrain