| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If the script finds a '[[ ]]' expression in the input file,
it will evaluate that expression and write out the result
in place of it. It will resolve both the MRW attributes and
any variables passed in from the command line first.
For example, if the attribute FOO has a value of 50 in the MRW,
and the program was started with: -v "MY_VAR1=200 MY_VAR2=400"
then the line
[[(MRW_FOO * MY_VAR1) + 5]]..[[MRW_FOO * MY_VAR2]]
would get written out as:
10005..20000
Change-Id: Ia7aa9ab61f99b5d9620d77fa1329bd6d7b0221bc
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is the first commit in a series to solve the problem
of needing to adjust an MRW attribute's value before writing
it back out to the settings override value.
This will be done by allowing mathematical expressions to
be present in the input file, and evaluating them to get
a final result that will get written out. These expressions
can also use variables whose names and values are passed in
from the command line.
This commit adds the ability to pass in the optional variables
and values from the command line with the -v argument, like:
-v "VAR1=VAL1 VAR2=VAL2"
Change-Id: I3baf47b38d6da25c5abdaae175ddfc6e97176927
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
|
| |
|
|
|
|
|
|
|
| |
Replace any MRW variables in the setting YAML with
their MRW value.
An MRW variable must be in the MRW_<MRW variable name> format.
Change-Id: Ic7e163beb4f5d13cae00ff2013b1c4080d39a256
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
|
|
|
Created gen_settings.pl, to be used to get settings boundary and
default values like OPEN_POWER_N_PLUS_ONE_BULK_POWER_LIMIT_WATTS
from the MRW. Just the base commit for gen_settings.pl, more to
come.
Change-Id: Iea68db8e588c114fa600c0d3e87f4d763f783c01
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
|
