| /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/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
|
| H A D | README.dfutftp | 52 Environment variables
64 1. Setup tftp env variables:
67 * setup "serverip" and "ipaddr" variables
80 2. Setup update_tftp variables:
87 4. Inspect "dfu" specific variables:
|
| /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/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.
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
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
70 repository CI settings, or as git push variables, to influence
84 * nnn - other misc variables not falling into the above
[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/linux/Documentation/filesystems/ |
| H A D | efivarfs.rst | 8 using entries in sysfs to maintain EFI variables. The old sysfs EFI
9 variables code only supported variables of up to 1024 bytes. This
11 removed before any full releases. Since variables can now be larger
22 UEFI variables causes the system firmware to fail to POST, efivarfs
23 files that are not well-known standardized variables are created
|
| H A D | gfs2-uevents.rst | 22 The ADD uevent has two environment variables: SPECTATOR=[0|1]
31 has the same environment variables as the ADD uevent. The ONLINE
32 uevent, along with the two environment variables for spectator and
46 two environment variables, JID= which specifies the journal id which
54 without checking the environment variables to discover the state, we
78 Information common to all GFS2 uevents (uevent environment 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/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/linux/Documentation/ABI/stable/ |
| H A D | sysfs-firmware-efi-vars | 6 EFI variables. For more information on EFI variables,
10 In summary, EFI variables are named, and are classified
15 The efivars module enumerates these variables and
32 explanation of each of these variables.
68 removing 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/linux/Documentation/livepatch/ |
| H A D | shadow-vars.rst | 5 Shadow variables are a simple way for livepatch modules to associate
9 to allocate/add and remove/free shadow variables to/from their parents.
17 variables may attach to the same parent object, but their numeric
26 A hashtable references all shadow variables. These references are
85 * klp_shadow_free_all() - detach and free all <_, id> shadow variables
111 be easiest to align their shadow variables lifetimes to the same
167 variables alongside their parent objects. Or a livepatch fix may
168 require shadow variables for only a subset of parent object instances.
170 shadow variables to parents already in-flight.
208 Shadow variables can also be used as a flag indicating that a data
[all …]
|
| /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/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 | 124 # Rules for use of data/variables.py
126 Avoid defining variables in data/variables.py for Redfish URIs.
128 There's no obvious benefit to using such variables. Conversely, with literal
133 Here's an excerpt from data/variables.py:
136 # Redfish variables.
|
| /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.
181 variables are not specifically set in the ``Makefile``, the variables
186 setting matching variables in the ``Makefile`` during the build
187 results in the environment settings of the variables being
188 overwritten. In this case, the variables you set in the ``Makefile``
194 environment variables being overwritten. In this case, the
199 Regardless of how you set your variables, if you use the "-e" option
[all …]
|
| /openbmc/openbmc-test-automation/lib/ |
| H A D | resource.robot | 6 Variables ../data/variables.py
32 # AUTH_SUFFIX here is derived from variables.py
156 # LDAP related variables.
170 # General tool variables
184 # Task Service related 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/linux/Documentation/networking/ |
| H A D | ioam6-sysctl.rst | 4 IOAM6 Sysfs variables
8 /proc/sys/net/conf/<iface>/ioam6_* variables:
|
| /openbmc/openbmc/poky/documentation/migration-guides/ |
| H A D | release-notes-4.3.1.rst | 115 - ref-manual: remove semicolons from ``*PROCESS_COMMAND`` variables
117 - ref-manual: variables: add :term:`RECIPE_MAINTAINER`
118 - ref-manual: variables: add :term:`RECIPE_SYSROOT` and :term:`RECIPE_SYSROOT_NATIVE`
119 - ref-manual: variables: add :term:`TOOLCHAIN_OPTIONS` variable
120 - ref-manual: variables: add example for :term:`SYSROOT_DIRS` variable
121 - ref-manual: variables: document :term:`OEQA_REPRODUCIBLE_TEST_PACKAGE`
122 - ref-manual: variables: mention new CDN for :term:`SSTATE_MIRRORS`
123 - ref-manual: variables: provide no-match example for :term:`COMPATIBLE_MACHINE`
124 - ref-manual: variables: remove SERIAL_CONSOLES_CHECK
|
| /openbmc/phosphor-time-manager/ |
| H A D | meson.options | 12 # Commandline variables list
13 # Value can be assigned from commandline to below variables
|