| /openbmc/phosphor-power/ |
| 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 …]
|
| H A D | json_parser_utils.hpp | 88 const std::map<std::string, std::string>& variables = NO_VARIABLES);
103 const std::map<std::string, std::string>& variables = NO_VARIABLES);
118 const std::map<std::string, std::string>& variables = NO_VARIABLES);
133 const std::map<std::string, std::string>& variables = NO_VARIABLES);
152 const std::map<std::string, std::string>& variables = NO_VARIABLES);
168 const std::map<std::string, std::string>& variables = NO_VARIABLES);
183 const std::map<std::string, std::string>& variables = NO_VARIABLES);
198 const std::map<std::string, std::string>& variables = NO_VARIABLES);
214 const std::map<std::string, std::string>& variables = NO_VARIABLES);
229 const std::map<std::string, std::string>& variables = NO_VARIABLES);
[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 | 744 std::map<std::string, std::string> variables{}; in TEST() local
746 parseChassisProperties(element, isChassisTemplate, variables); 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()
855 std::map<std::string, std::string> variables{}; in TEST() local
856 parseChassisProperties(element, isChassisTemplate, variables); in TEST()
[all …]
|
| /openbmc/phosphor-power/phosphor-power-sequencer/src/ |
| 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 …]
|
| H A D | config_file_parser.hpp | 148 const std::map<std::string, std::string>& variables);
202 const json& element, const std::map<std::string, std::string>& variables);
216 const std::map<std::string, std::string>& variables);
230 const json& element, const std::map<std::string, std::string>& variables);
244 const json& element, const std::map<std::string, std::string>& variables);
258 const json& element, const std::map<std::string, std::string>& variables);
272 const json& element, const std::map<std::string, std::string>& variables);
286 const json& element, const std::map<std::string, std::string>& variables);
|
| /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/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/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/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/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/poky/bitbake/bin/ |
| H A D | toaster-eventreplay | 38 variables = None
41 variables = json.loads(line)['allvariables']
45 if not variables:
49 player = eventreplay.EventPlayer(eventfile, variables)
|
| /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/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/openbmc/poky/bitbake/doc/bitbake-user-manual/ |
| H A D | bitbake-user-manual-ref-variables-context.rst | 29 Those variables are usually configured globally.
34 There are variables:
37 BitBake during the build of a particular recipe. Those variables are
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``.
79 - In recipes, variables are also used to control build and runtime
84 - There are further variables starting with ``SRC`` that specify the sources in
89 multiple recipes would provide the same item, is controlled by 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/poky/meta/lib/oeqa/utils/ |
| H A D | commands.py | 248 def get_bb_vars(variables=None, target=None, postconfig=None): argument
252 if variables is not None:
253 variables = list(variables)
271 if variables is None:
274 if var in variables:
276 variables.remove(var)
278 if not variables:
281 if variables:
283 for var in variables:
|
| /openbmc/openbmc/meta-phosphor/recipes-phosphor/clear-once/ |
| H A D | clear-once.bb | 1 SUMMARY = "Clear boot-once variables"
2 DESCRIPTION = "Clear u-boot variables used for one-time boot flow"
|
| /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
34 # AUTH_SUFFIX here is derived from variables.py
158 # LDAP related variables.
172 # General tool variables
186 # Task Service related variables.
|
| /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-*`.
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
148 color palette can be customized. Using these variables outside of the helper
[all …]
|
| /openbmc/phosphor-time-manager/ |
| H A D | meson.options | 12 # Commandline variables list
13 # Value can be assigned from commandline to below variables
|
| /openbmc/openbmc/poky/bitbake/lib/bb/ |
| H A D | data_smart.py | 245 self.variables = COWDictBase.copy()
249 new.variables = self.variables.copy()
254 for k, v in self.variables.iteritems():
261 self.variables = COWDictBase.copy()
263 self.variables[k] = v
278 if var not in self.variables:
279 self.variables[var] = []
280 if not isinstance(self.variables[var], list):
282 if 'nodups' in loginfo and loginfo in self.variables[var]:
284 self.variables[var].append(loginfo.copy())
[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.
|
| /openbmc/openbmc/meta-evb/meta-evb-arm/meta-evb-fvp-base/recipes-bsp/u-boot/files/ |
| H A D | fvp.env | 1 # variables
6 # runnable variables in order of execution (for readability)
|