| /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/qemu/.gitlab-ci.d/ |
| H A D | container-cross.yml | 4 variables:
10 variables:
16 variables:
22 variables:
28 variables:
34 variables:
40 variables:
46 variables:
52 variables:
58 variables:
[all …]
|
| H A D | crossbuilds.yml | 8 variables:
15 variables:
22 variables:
29 variables:
39 variables:
50 variables:
61 variables:
75 variables:
82 variables:
89 variables:
[all …]
|
| H A D | buildtest.yml | 10 variables:
21 variables:
30 variables:
40 variables:
51 variables:
60 variables:
70 variables:
82 variables:
91 variables:
100 variables:
[all …]
|
| H A D | containers.yml | 7 variables:
13 variables:
18 variables:
23 variables:
28 variables:
33 variables:
|
| /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/src/ |
| H A D | config_file_parser.hpp | 136 * @param variables variables map used to expand variables in element value
142 const std::map<std::string, std::string>& variables, Services& services);
150 * template that contains variables.
154 * template variables.
157 * re-parsed, and the template variables will be replaced with the
192 * @param variables variables map used to expand variables in element value
196 const std::map<std::string, std::string>& variables);
206 * @param variables variables map used to expand variables in element value
210 const json& element, const std::map<std::string, std::string>& variables);
220 * @param variables variables map used to expand variables in element value
[all …]
|
| H A D | config_file_parser.cpp | 131 std::map<std::string, std::string> variables = in parseChassis() local
149 return parseChassisProperties(templateElement, isChassisTemplate, variables, in parseChassis()
170 const std::map<std::string, std::string>& variables, Services& services) in parseChassisProperties() argument
192 unsigned int number = parseUnsignedInteger(numberElement, variables); in parseChassisProperties()
203 parseString(inventoryPathElement, false, variables); in parseChassisProperties()
210 parsePowerSequencerArray(powerSequencersElement, variables, services); in parseChassisProperties()
271 const std::map<std::string, std::string>& variables) in parseGPIO() argument
278 unsigned int line = parseUnsignedInteger(lineElement, variables); in parseGPIO()
286 activeLow = parseBoolean(*activeLowIt, variables); in parseGPIO()
298 const std::map<std::string, std::string>& variables) in parseI2CInterface() argument
[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/phosphor-power/phosphor-power-sequencer/test/ |
| H A D | config_file_parser_tests.cpp | 731 // Test where works: Parse chassis object without template/variables: Has in TEST()
751 std::map<std::string, std::string> variables{}; in TEST() local
754 variables, services); in TEST()
773 // Test where works: Parse chassis_template object with variables: No in TEST()
793 std::map<std::string, std::string> variables{ in TEST() local
797 variables, services); in TEST()
819 std::map<std::string, std::string> variables{}; in TEST() local
821 parseChassisProperties(element, isChassisTemplate, variables, services); in TEST()
840 std::map<std::string, std::string> variables{{"chassis_number", "2"}}; in TEST() local
842 parseChassisProperties(element, isChassisTemplate, variables, services); in TEST()
[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/qemu/docs/devel/testing/ |
| H A D | ci-jobs.rst.inc | 3 Custom CI/CD variables
6 QEMU CI pipelines can be tuned by setting some CI environment variables.
11 Variables can be set globally in the user's CI namespace setting.
13 For further information about how to set these variables, please refer to::
15 https://docs.gitlab.com/ee/ci/variables/#add-a-cicd-variable-to-a-project
20 Variables can be set manually when pushing a branch or tag, using
29 For further information about how to set these variables, please refer to::
62 The variables used by QEMU's CI configuration are grouped together
65 * QEMU_JOB_nnnn - variables to be defined in individual jobs
69 * QEMU_CI_nnn - variables to be set by contributors in their
[all …]
|
| /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 …]
|
| /openbmc/phosphor-power/phosphor-power-sequencer/docs/config_file/ |
| H A D | chassis_template.md | 12 chassis. One or more property values in the template contain variables, such as
16 The individual chassis specify values for the template variables, such as
19 ### Template Variables
21 Variables are specified in property values of a chassis template. This includes
30 Variables can be specified as the entire property value or as part of the
38 Variables are supported for the property types string, number, and boolean.
40 Variables must be specified within a string value (surrounded by double quotes).
|
| /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. */
|