| /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:
41 variables:
52 variables:
61 variables:
72 variables:
84 variables:
93 variables:
103 variables:
[all …]
|
| H A D | containers.yml | 7 variables:
13 variables:
18 variables:
23 variables:
28 variables:
33 variables:
|
| /openbmc/linux/drivers/gpu/drm/ci/ |
| H A D | test.yml | 24 variables:
39 variables:
54 variables:
71 variables:
90 variables:
103 variables:
122 variables:
136 variables:
148 variables:
162 variables:
[all …]
|
| H A D | build.yml | 18 variables:
29 variables:
38 variables:
65 variables:
77 variables:
89 variables:
107 variables:
|
| H A D | container.yml | 2 variables:
7 variables:
11 variables:
15 variables:
19 variables:
|
| /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 …]
|
| H A D | bitbake-user-manual-execution.rst | 66 The ``layer.conf`` files are used to construct key variables such as
80 variables, including:
88 The first four variables in this list relate to how BitBake treats shell
89 environment variables during task execution. By default, BitBake cleans
90 the environment variables and provides tight control over the shell
92 variables, you can apply your control regarding the environment
93 variables allowed to be used by BitBake in the shell during execution of
96 section and the information about these variables in the variable
107 set the :term:`BBPATH` and :term:`BBFILES` variables directly in the
114 variables correctly for a given build directory.
[all …]
|
| /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/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/linux/include/xen/interface/ |
| H A D | platform.h | 23 /* IN variables. */
31 /* IN variables. */
48 /* IN variables. */
52 /* OUT variables. */
67 /* IN variables. */
76 /* IN variables. */
78 /* OUT variables. */
87 /* IN variables. */
98 /* IN variables. */
211 /* IN variables. */
[all …]
|
| /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/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
14 Variables can be created, deleted and modified with the efivarfs
22 UEFI variables causes the system firmware to fail to POST, efivarfs
23 files that are not well-known standardized variables are created
|
| /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/linux/Documentation/livepatch/ |
| H A D | shadow-vars.rst | 2 Shadow Variables
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.
[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 …]
|
| /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/openbmc-test-automation/lib/ |
| 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/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/drivers/net/fddi/skfp/h/ |
| H A D | sba.h | 32 * Node variables
53 * Session variables
81 * variables for allocation actions
102 * SBA variables
108 * SBA state machine variables
118 * variables for the End Station Support
133 * variables for the ess bandwidth control
|
| /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/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)
|