param: workaround for QURT

There is no such thing as set_param_no_autosave on QURT, therefore just
save it anyway. On the Snapdragon the overhead should not be a problem.
This commit is contained in:
Julian Oes
2016-02-16 21:15:31 +01:00
parent 10afd4abb4
commit 3cda3610d0
+12 -2
View File
@@ -448,7 +448,12 @@ do_set(const char *name, const char *val, bool fail_on_not_found)
param_value_unsaved(param) ? '*' : (param_value_is_default(param) ? ' ' : '+'),
param_name(param));
printf("curr: %ld", (long)i);
//param_set_no_autosave(param, &newval);
// FIXME: the call paramset_no_autosave doesn't exist on Eagle yet.
#ifndef CONFIG_ARCH_BOARD_EAGLE
param_set_no_autosave(param, &newval);
#else
param_set(param, &newval);
#endif
printf(" -> new: %ld\n", (long)newval);
}
}
@@ -470,7 +475,12 @@ do_set(const char *name, const char *val, bool fail_on_not_found)
param_value_unsaved(param) ? '*' : (param_value_is_default(param) ? ' ' : '+'),
param_name(param));
printf("curr: %4.4f", (double)f);
//param_set_no_autosave(param, &newval);
// FIXME: the call paramset_no_autosave doesn't exist on Eagle yet.
#ifndef CONFIG_ARCH_BOARD_EAGLE
param_set_no_autosave(param, &newval);
#else
param_set(param, &newval);
#endif
printf(" -> new: %4.4f\n", (double)newval);
}