commit 44af3415a5b1d1e8348b81d983578f3cd8ac05f9
author Your Name <you@example.com> Thu Apr 13 03:11:59 2017 +0200
committer Neels Hofmeyr <nhofmeyr@sysmocom.de> Thu Apr 13 03:39:07 2017 +0200
tree 3cb8327c84bbc1613bf28483ab871009a447094a
parent 17c139ef4c8aaea9477ba34092fe453afd417c49

fix octphy, fix conf, improve logging

Clearly separate the kinds of BTS hardware the GSM tester knows ('type') from
the NITB's bts/type config item ('osmobsc_bts_type' -- not 'osmonitb_...' to
stay in tune with future developments: it is the libbsc that needs this).

For BTS hardware kinds, use the full name of the binary for osmo driven models:
osmo-bts-sysmo, osmo-bts-trx, osmo-bts-octphy.

Change-Id: I1aa9b48e74013a93f9db1a34730f17717fb3b36c

selftest/real_suite/resources.conf

diff --git a/selftest/real_suite/resources.conf b/selftest/real_suite/resources.conf
index 3a5b129..c6573ee 100644
--- a/selftest/real_suite/resources.conf
+++ b/selftest/real_suite/resources.conf
@@ -7,22 +7,22 @@
 
 bts:
 - label: sysmoBTS 1002
-  type: sysmo
+  type: osmo-bts-sysmo
   ipa_unit_id: 1
   addr: 10.42.42.114
   band: GSM-1800
 
 - label: octBTS 3000
-  type: oct
+  type: osmo-bts-octphy
   ipa_unit_id: 5
   addr: 10.42.42.115
   band: GSM-1800
-  trx:
+  trx_list:
   - hw_addr: 00:0c:90:32:b5:8a
     net_device: eth0.2342
 
 - label: Ettus B210
-  type: osmotrx
+  type: osmo-bts-trx
   ipa_unit_id: 6
   addr: 10.42.42.116
   band: GSM-1800
@@ -32,7 +32,7 @@
   ipa_unit_id: 1902
   addr: 10.42.42.190
   band: GSM-1900
-  trx:
+  trx_list:
   - hw_addr: 00:02:95:00:41:b3
 
 arfcn: