Remove explicit test debug_threshold from SCT files and regenerate

This commit is contained in:
Douglas Clowes
2014-07-21 10:58:01 +10:00
parent 0becbe914a
commit ab3d7c5adf
9 changed files with 8 additions and 15 deletions

View File

@@ -1,5 +1,4 @@
driver astrium_chopper = {
debug_threshold = 2;
vendor = astrium; device = chopper; protocol = std;
class = NXdisk_chopper; simulation_group = chopper_simulation;
@@ -108,6 +107,5 @@ driver astrium_chopper = {
%%}
code mkDriver = {%%
hsetprop ${scobj_hpath} debug_threshold 1
%%}
}

View File

@@ -3,7 +3,7 @@
#
namespace eval ::scobj::astrium_chopper {
set debug_threshold 2
set debug_threshold 5
}
proc ::scobj::astrium_chopper::debug_log {tc_root debug_level debug_string} {
@@ -526,9 +526,8 @@ proc ::scobj::astrium_chopper::mkDriver { sct_controller name } {
::scobj::astrium_chopper::sics_log 9 "[chopper_simulation] => No poll/write for astrium_chopper"
}
hsetprop ${scobj_hpath} klass NXdisk_chopper
hsetprop ${scobj_hpath} debug_threshold 2
hsetprop ${scobj_hpath} debug_threshold 5
# mkDriver hook code starts
hsetprop ${scobj_hpath} debug_threshold 1
# mkDriver hook code ends
} catch_message ]
handle_exception ${catch_status} ${catch_message}