* there is a subproject that is included as a subtree in
  common/ip/tapasco_status
* subproject is standalone and can be run from Tcl
* changed process in common.tcl: createTapascoStatus now generates a
  JSON configuration file and runs sbt in the subproject
* each Composition gets its unique status core
* status cores are cached in tapasco-status-cache in the main dir:
  when building the same composition a number of times, status cores can
  be reused; is removed automatically in sbt clean
* required more API extensions: platform::get_address_map must be
  implemented by the Platform to communicate the address mapping to the
  status core creation
* also added formal interface to capabilities in common.tcl:
  tapasco::add_capability_flag, tapasco::get_capability_flags and
  tapasco::set_capability_flags can be used by plugins to activate
  capability bits
* whole process should be transparent to the user, everything is
  supposed to work as before
* one exception: get_address_map is not yet implemented on VC709

Merge commit 'f94b6de3' into pe-local-memories

* following an internal discussion, we'd rather be sure to build
  everything from scratch in the runner, or version hell ensues

Merge commit '5a089419'

* empty slots did not exist at all, resulting in reads/writes causing
  bus errors, crash
* new Slot type Empty represents an empty slot
* slots in status configuration are filled with empty slots to fix the
  problem
* should not increase the size significantly; all empty slots are
  represented by the same ConstantRegister

git-subtree-dir: common/ip/tapasco_status
git-subtree-mainline: 225cfa31
git-subtree-split: e209f949

Merge commit 'a9f329c5'

* zero-width io ports must be assigned, or compilation will fail
* fixed RegisterFileSpec accordingly
* updated to Scala 2.11.12

* re-used generic test from RegisterFile
* status configuration is generated by spec gens

Merge commit '8d79675d'

* Builder class main uses first argument as path to JSON config file
* IP Core is generated under ip/ hierarchy: each configuration hash is
  unique and can be used to cache products
* sbt clean removes this cache
* example.json contains an example configuration

* JsonSpec checks that roundtrips to and from Json preserve all data
* generators package contains ScalaCheck generators

* Status contains complete configuration, including kernel ids, memory
  slots and some basic sanity checking
* json package contains JSON SerDes functionality

* started with external format (JSON)
* noticed a problem: without Verilog module parameters Features cannot
  easily add capabilities etc.
* postponing the project until later