| /openbmc/phosphor-power/ |
| H A D | json_parser_utils.hpp | 31 * ## Variables
32 * The parsing functions support optional usage of variables. JSON string values
33 * can contain one or more variables. A variable is specified using the format
34 * `${variable_name}`. A variables map is specified to parsing functions that
38 * Variables can only appear in a JSON string value. The parsing functions for
47 * Empty variables map used as a default value for parsing functions.
83 * @param variables variables map used to expand variables in element value
88 const std::map<std::string, std::string>& variables = NO_VARIABLES);
98 * @param variables variables map used to expand variables in element value
103 const std::map<std::string, std::string>& variables = NO_VARIABLES);
[all …]
|
| H A D | json_parser_utils.cpp | 30 const std::map<std::string, std::string>& variables) in parseBitPosition() argument
32 int value = parseInteger(element, variables); in parseBitPosition()
41 const std::map<std::string, std::string>& variables) in parseBitValue() argument
43 int value = parseInteger(element, variables); in parseBitValue()
52 const std::map<std::string, std::string>& variables) in parseBoolean() argument
59 if (element.is_string() && !variables.empty()) in parseBoolean()
61 std::string value = parseString(element, true, variables); in parseBoolean()
76 const std::map<std::string, std::string>& variables) in parseDouble() argument
83 if (element.is_string() && !variables.empty()) in parseDouble()
85 std::string strValue = parseString(element, true, variables); in parseDouble()
[all …]
|
| /openbmc/phosphor-power/phosphor-power-sequencer/src/ |
| H A D | config_file_parser.hpp | 143 * @param variables variables map used to expand variables in element value
148 const std::map<std::string, std::string>& variables);
156 * template that contains variables.
160 * template variables.
163 * re-parsed, and the template variables will be replaced with the
198 * @param variables variables map used to expand variables in element value
202 const json& element, const std::map<std::string, std::string>& variables);
212 * @param variables variables map used to expand variables in element value
216 const std::map<std::string, std::string>& variables);
226 * @param variables variables map used to expand variables in element value
[all …]
|
| H A D | config_file_parser.cpp | 136 std::map<std::string, std::string> variables = in parseChassis() local
155 variables); in parseChassis()
173 const std::map<std::string, std::string>& variables) in parseChassisProperties() argument
195 unsigned int number = parseUnsignedInteger(numberElement, variables); in parseChassisProperties()
206 parseString(inventoryPathElement, false, variables); in parseChassisProperties()
213 parsePowerSequencerArray(powerSequencersElement, variables); in parseChassisProperties()
221 monitorOptions = parseStatusMonitoring(*statusMonitoringIt, variables); in parseChassisProperties()
290 const json& element, const std::map<std::string, std::string>& variables) in parseStatusMonitoring() argument
302 options.isPresentMonitored = parseBoolean(*propIt, variables); in parseStatusMonitoring()
310 options.isAvailableMonitored = parseBoolean(*propIt, variables); in parseStatusMonitoring()
[all …]
|
| /openbmc/phosphor-power/test/ |
| H A D | json_parser_utils_tests.cpp | 72 std::map<std::string, std::string> variables{{"bit_pos", "3"}}; in TEST() local
74 uint8_t value = parseBitPosition(element, variables); in TEST()
117 std::map<std::string, std::string> variables{{"bit_pos", "-1"}}; in TEST() local
119 parseBitPosition(element, variables); in TEST()
146 std::map<std::string, std::string> variables{{"bit_val", "1"}}; in TEST() local
148 uint8_t value = parseBitValue(element, variables); in TEST()
191 std::map<std::string, std::string> variables{{"bit_val", "one"}}; in TEST() local
193 parseBitValue(element, variables); in TEST()
220 std::map<std::string, std::string> variables{{"bool_val", "true"}}; in TEST() local
222 bool value = parseBoolean(element, variables); in TEST()
[all …]
|
| /openbmc/phosphor-power/phosphor-power-sequencer/test/ |
| H A D | config_file_parser_tests.cpp | 723 // Test where works: Parse chassis object without template/variables: Has in TEST()
744 std::map<std::string, std::string> variables{}; in TEST() local
746 parseChassisProperties(element, isChassisTemplate, variables); in TEST()
766 // Test where works: Parse chassis_template object with variables: No in TEST()
787 std::map<std::string, std::string> variables{ in TEST() local
793 parseChassisProperties(element, isChassisTemplate, variables); in TEST()
816 std::map<std::string, std::string> variables{}; in TEST() local
817 parseChassisProperties(element, isChassisTemplate, variables); in TEST()
836 std::map<std::string, std::string> variables{{"chassis_number", "2"}}; in TEST() local
837 parseChassisProperties(element, isChassisTemplate, variables); in TEST()
[all …]
|
| /openbmc/openbmc/poky/bitbake/doc/bitbake-user-manual/ |
| H A D | bitbake-user-manual-ref-variables-context.rst | 9 Variables might only have an impact or can be used in certain contexts. Some
19 Variables starting with ``BB_`` usually configure the behaviour of BitBake itself.
29 Those variables are usually configured globally.
34 There are variables:
37 BitBake during the build of a particular recipe. Those variables are
53 Variables starting with ``LAYER`` configure how BitBake handles layers.
54 Additionally, variables starting with ``BB`` configure how layers and files are
63 Those variables are often used in the files ``layer.conf`` and ``bblayers.conf``.
68 Variables handling recipes and packages can be split into:
79 - In recipes, variables are also used to control build and runtime
[all …]
|
| /openbmc/openbmc/poky/documentation/ref-manual/ |
| H A D | varlocality.rst | 7 While you can use most variables in almost any context such as
8 ``.conf``, ``.bbclass``, ``.inc``, and ``.bb`` files, some variables are
17 The following subsections provide lists of variables whose context is
25 This section lists variables whose configuration context is the
51 This section lists variables whose configuration context is the machine.
76 This section lists variables whose configuration context is the local
102 The following subsections provide lists of variables whose context is
110 This section lists variables that are required for recipes.
123 This section lists variables that define recipe dependencies.
140 This section lists variables that define recipe paths.
[all …]
|
| /openbmc/qemu/qapi/ |
| H A D | uefi.json | 11 # store non-volatile variables in json format on disk.
33 # string. Used only for authenticated variables, where the
38 # of updates for authenticated variables. UEFI has two kinds of
39 # authenticated variables. The secure boot variables ('PK',
41 # For other authenticated variables the firmware stores a digest
60 # @variables: list of UEFI variables
66 'variables' : [ 'UefiVariable' ] }}
|
| /openbmc/webui-vue/src/assets/styles/bootstrap/ |
| H A D | _index.scss | 4 // Import our custom colors and variables before Bootstrap variables
6 @import "../bmc/helpers/variables";
8 // Import Bootstrap variables and maps
9 @import "~bootstrap/scss/variables";
13 // Import our custom functions that depend on Bootstrap variables
|
| /openbmc/openbmc-test-automation/data/ |
| H A D | variables.py | 33 # Sensors base variables.
35 # Thermal Control base variables
41 # State Manager base variables
55 # State Manager URI variables.
65 # Logging URI variables
100 # Inventory URI variables
115 # Host control URI variables.
118 # Power restore variables.
126 # Dump URI variables.
133 # Boot progress variables.
[all …]
|
| /openbmc/openbmc/poky/documentation/sdk-manual/ |
| H A D | working-projects.rst | 140 To learn about environment variables established when you run the
164 environment variables established when you run the cross-toolchain
165 environment setup script. The environment variables are subject to
170 variables and Makefile variables during development.
179 - *Case 1 --- No Variables Set in the Makefile Map to Equivalent
180 Environment Variables Set in the SDK Setup Script:* Because matching
181 variables are not specifically set in the ``Makefile``, the variables
184 - *Case 2 --- Variables Are Set in the Makefile that Map to Equivalent
185 Environment Variables from the SDK Setup Script:* Specifically
186 setting matching variables in the ``Makefile`` during the build
[all …]
|
| /openbmc/u-boot/board/keymile/scripts/ |
| H A D | README | 5 To load and configure these usecase, two environment variables in the u-boot
14 This file defines variables for working with rootfs via nfs for powerpc and
19 This file defines architecture specific variables for working with rootfs via
25 This file defines variables for working with rootfs inside the ram for powerpc
30 This file defines architecture specific variables for working with rootfs inside
|
| /openbmc/openbmc/poky/bitbake/lib/bb/ui/ |
| H A D | eventreplay.py | 20 def __init__(self, eventfile, variables): argument
22 self.variables = variables
33 self.variables = decodedline['allvariables']
53 variable = self.variables.get(var_name)
61 for key, val in self.variables.items():
|
| /openbmc/webui-vue/docs/customization/ |
| H A D | theme.md | 5 libraries. This section outlines the global options and variables that can be
25 these built-in variables is `enabled-*`.
44 ## Bootstrap Sass Variables
46 These are global variables that Bootstrap defines in the
47 `/node_modules/bootstrap/scss/variables.scss` helper file. Adding a variable
130 palette is supported using the Sass variables outlined in the color guidelines
136 The OpenBMC Web UI uses Sass variables and maps to build its layout and
137 components. Bootstrap variables and maps use the `!default` flag to allow for
144 The OpenBMC Web UI custom colors are available as Sass variables and a Sass map
147 Adding, removing, or updating the color variables and map is how the application
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-perl/recipes-perl/libenv/ |
| H A D | libenv-perl_1.04.bb | 1 SUMMARY = "Perl module that imports environment variables as scalars or arrays"
2 DESCRIPTION = "Perl maintains environment variables in a special hash named %ENV. \
4 variables to be treated as scalar or array variables."
|
| /openbmc/u-boot/doc/ |
| H A D | README.at91 | 18 Environment variables
20 U-Boot environment variables can be stored at different places:
40 Environment variables
42 U-Boot environment variables can be stored at different places:
61 Environment variables
63 U-Boot environment variables can be stored at different places:
84 Environment variables
86 U-Boot environment variables can be stored at different places:
101 Environment variables
103 U-Boot environment variables can be stored at different places:
[all …]
|
| H A D | README.spear | 36 spear320 build with environment variables placed at default
40 for CFI compliant parallel NOR flash. Environment variables are
43 spear320 build with environment variables placed in NAND device
73 environment variables. Although, we can check the mac id programmed in i2c
|
| /openbmc/openbmc/poky/bitbake/bin/ |
| H A D | toaster-eventreplay | 37 # load variables from the first line
38 variables = None
41 variables = json.loads(line)['allvariables']
45 if not variables:
49 player = eventreplay.EventPlayer(eventfile, variables)
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/trusted-firmware-m/files/corstone1000/ |
| H A D | 0006-Platform-CS1000-Increase-buffers-for-EFI-vars.patch | 6 The UEFI variables are stored in the Protected Storage. The size of
7 the variables metadata have been increased in the Host software stack
10 - The PS_MAX_ASSET_SIZE needs to be big enough to store the variables.
34 +/* This is needed to be able to process the EFI variables during PS writes. */
37 +/* This is also has to be increased to fit the EFI variables into the iovecs. */
|
| /openbmc/openbmc-test-automation/lib/ |
| H A D | resource.robot | 2 Documentation Base resource file variables used for all context
8 Variables ../data/variables.py
10 *** Variables ***
34 # AUTH_SUFFIX here is derived from variables.py
158 # LDAP related variables.
172 # General tool variables
186 # Task Service related variables.
|
| H A D | gen_robot_utils.py | 38 *** Variables ***
53 - The problems with -v parms mentioned above are also found with variables
54 from your file_x.robot "** Variables **" section. Namely, they may get
60 # Retrieve the values of all current variables into a dictionary.
64 # Once again, retrieve the values of all current variables into a
|
| H A D | gen_plug_in_utils.py | 41 … an OrderedDict which is sorted by key and which contains all of the plug-in environment variables.
54 - Register PASSWORD variables to prevent their values from being printed.
66 … non-string type in setting global variables (with the exception of os.environ values which must be
104 …# For all variables specified in the parm_def file, we want them to default to "" rather than bein…
122 …# Create a list of plug-in environment variables by pre-pending <all caps plug-in package name>_<a…
155 # Restore the types of any variables where the caller had defined default values.
182 …Sprint the plug-in environment variables (i.e. those that begin with the global PLUG_VAR_PREFIX va…
212 …When debug is set, print all plug_prefix variables (e.g. AUTOBOOT_OPENBMC_HOST, etc.) and all plug…
213 …environment variables (e.g. OBMC_SAMPLE_PARM1) with surrounding dashed lines. When debug is not s…
214 …print only the plug-in environment variables (e.g. OBMC_SAMPLE_PARM1) with no surrounding dashed l…
[all …]
|
| /openbmc/u-boot/cmd/ |
| H A D | nvedit_efi.c | 3 * Integrate UEFI variables to u-boot env interface
20 * Mapping between UEFI variables and u-boot variables:
88 * efi_dump_vars() - show information about named UEFI variables
90 * @argc: Number of arguments (variables)
94 * Show information encoded in named UEFI variables
131 * efi_dump_vars() - show information about all the UEFI variables
135 * Show information encoded in all the UEFI variables
182 * do_env_print_efi() - show information about UEFI variables
193 * named UEFI variables, otherwise show all the UEFI variables.
208 /* show specified UEFI variables */ in do_env_print_efi()
[all …]
|
| /openbmc/openbmc-test-automation/docs/ |
| H A D | redfish_coding_guidelines.md | 121 # Rules for use of data/variables.py
123 Avoid defining variables in data/variables.py for Redfish URIs.
125 There's no obvious benefit to using such variables. Conversely, with literal
130 Here's an excerpt from data/variables.py:
133 # Redfish variables.
|