| /openbmc/openbmc-test-automation/tools/ |
| H A D | generate_argumentfile.sh | 3 echo "--variable OPENBMC_HOST:$OPENBMC_HOST" > $ARG_FILE
4 echo "--variable OPENBMC_MODEL:$OPENBMC_MODEL" >> $ARG_FILE
5 echo "--variable OPENBMC_USERNAME:$OPENBMC_USERNAME" >> $ARG_FILE
6 echo "--variable OPENBMC_PASSWORD:$OPENBMC_PASSWORD" >> $ARG_FILE
7 echo "--variable OPENBMC_SYSTEMMODEL:$OPENBMC_SYSTEMMODEL" >> $ARG_FILE
8 echo "--variable GUI_BROWSER:$GUI_BROSWER" >> $ARG_FILE
9 echo "--variable GUI_MODE:$GUI_MODE" >> $ARG_FILE
10 echo "--variable PDU_TYPE:$PDU_TYPE" >> $ARG_FILE
11 echo "--variable PDU_IP:$PDU_IP" >> $ARG_FILE
12 echo "--variable PDU_USERNAME:$PDU_USERNAME" >> $ARG_FILE
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/vpnc/vpnc/ |
| H A D | long-help | 6 conf-variable: IPSec gateway <ip/hostname>
10 conf-variable: IPSec ID <ASCII string>
14 conf-variable: IPSec secret <ASCII string>
18 conf-variable: IPSec obfuscated secret <hex string>
22 conf-variable: Xauth username <ASCII string>
26 conf-variable: Xauth password <ASCII string>
30 conf-variable: Xauth obfuscated password <hex string>
34 conf-variable: Domain <ASCII string>
38 conf-variable: Xauth interactive
43 conf-variable: Vendor <cisco/netscreen>
[all …]
|
| /openbmc/u-boot/lib/efi_loader/ |
| H A D | efi_variable.c | 54 * efi_to_native() - convert the UEFI variable name and vendor GUID to U-Boot
55 * variable name
57 * The U-Boot variable name is a concatenation of prefix 'efi', the hexstring
58 * encoded vendor GUID, and the UTF-8 encoded UEFI variable name separated by
61 * @native: pointer to pointer to U-Boot variable name
62 * @variable_name: UEFI variable name
102 * parse_attr() - decode attributes part of variable value
104 * Convert the string encoded attributes of a UEFI variable to a bit mask.
107 * @str: value of U-Boot variable
109 * Return: pointer to remainder of U-Boot variable value
[all …]
|
| /openbmc/openbmc-test-automation/oem/nuvoton/ |
| H A D | test_jtag_master.robot | 23 Set Global Variable ${wrong_cpld} 1
25 Set Global Variable ${wrong_cpld} 0
63 ${status}= Run Keyword And Return Status Variable Should Exist
65 ${value}= Set Variable if ${status} == ${TRUE} ${TEST_PROGRAM_CPLD} 0
66 Set Global Variable ${program_cpld} ${value}
72 ${cpld_firmware1}= Set Variable ${olympus_json["npcm7xx"]["cpld"]["fw1"]}
73 ${cpld_firmware2}= Set Variable ${olympus_json["npcm7xx"]["cpld"]["fw2"]}
74 ${firmware_version1}= Set Variable ${olympus_json["npcm7xx"]["cpld"]["fw1ver"]}
75 ${firmware_version2}= Set Variable ${olympus_json["npcm7xx"]["cpld"]["fw2ver"]}
76 ${readusercode_svf}= Set Variable ${olympus_json["npcm7xx"]["cpld"]["readusercode"]}
[all …]
|
| /openbmc/openbmc-test-automation/lib/ |
| H A D | valid.tcl | 10 …# If the value of the variable named in var_name is not valid, print an error message and exit the…
14 # var_name The name of the variable whose value is to be validated.
15 …# invalid_values A list of invalid values. If the variable value is equal to any…
22 # your variable is non blank.
23 …# valid_values A list of invalid values. The variable value must be equal to o…
26 # Call get_stack_var_level to relieve the caller of the need for declaring the variable as global.
28 # Access the variable value.
53 append error_message "The following variable has an invalid value:\n"
74 append error_message "The following variable has an invalid value:\n"
90 …# If the value of the list variable named in var_name is not valid, print an error message and exi…
[all …]
|
| /openbmc/openbmc/poky/bitbake/lib/toaster/toastergui/templates/ |
| H A D | configvars.html | 15 {{objects.paginator.count}} variable{{objects.paginator.count|pluralize}} found
55 {% for variable in objects %}
57 …<td class="variable_name"><a data-toggle="modal" href="#variable-{{variable.pk}}">{{variable.varia…
58 <td class="variable_value">{{variable.variable_value|truncatechars:153}}</td>
60 {% if variable.vhistory.all %}
61 {% for path in variable.vhistory.all|filter_setin_files:file_filter %}
67 {% if variable.description %}
68 {{variable.description}}
69 …<a href="http://docs.yoctoproject.org/ref-manual/variables.html#term-{{variable.variable_name|vari…
83 {% for variable in objects %}
[all …]
|
| /openbmc/webui-vue/docs/.vuepress/components/colors/ |
| H A D | grays.vue | 11 <dt>Color variable:</dt>
12 <dd>${{ color.variable }}</dd>
29 variable: 'gray-100',
34 variable: 'gray-200',
38 variable: 'gray-300',
42 variable: 'gray-400',
46 variable: 'gray-500',
50 variable: 'gray-600',
54 variable: 'gray-700',
58 variable: 'gray-800',
[all …]
|
| H A D | theme.vue | 11 <dt>Color variable:</dt>
15 <dt>Color variable:</dt>
16 <dd>${{ item.variable }}</dd>
30 variable: "blue",
35 variable: "gray-800",
40 variable: 'gray-100',
46 variable: 'gray-900',
51 variable: 'blue',
56 variable: 'green',
61 variable: 'yellow',
[all …]
|
| H A D | all.vue | 11 <dt>Variable:</dt>
15 <dt>Color Variable:</dt>
16 <dd>{{ item.variable }}</dd>
30 variable: '$blue-500',
35 variable: '$green-500',
40 variable: '$red-500',
45 variable: '$yellow-500',
|
| /openbmc/phosphor-power/phosphor-power-sequencer/docs/config_file/ |
| H A D | template_variable_values.md | 5 Template variable values for a specific chassis.
15 Each chassis using a template must specify values for each template variable.
19 All chassis variable values are specified as a string (surrounded by double
20 quotes). If the property value where the variable occurs has a different data
27 | Variable 1 name (see [notes](#notes)) | yes | string | Value of the template variable with t…
28 | Variable 2 name (see [notes](#notes)) | yes | string | Value of the template variable with t…
30 | Variable N name (see [notes](#notes)) | yes | string | Value of the template variable with t…
34 - The variable names are defined in the chassis template, such as
36 - The variable name must be specified without the "$", "{", and "}" characters.
|
| /openbmc/u-boot/tools/env/ |
| H A D | fw_env.h | 27 * @argv: array of variable names to be printed, if argc != 0
28 * @value_only: do not repeat the variable name, print the bare value,
29 * only one variable allowed with this option, argc must be 1
41 * fw_env_set() - adds or removes one variable to the environment
43 * @argc: number of strings in argv, argv[0] is variable name,
44 * argc==1 means erase variable, argc > 1 means add a variable
45 * @argv: argv[0] is variable name, argv[1..argc-1] are concatenated separated
46 * by single blank and set as the new value of the variable
78 * A variable without value will be deleted. Any number of spaces are allowed
91 * # delete variable bar
[all …]
|
| /openbmc/u-boot/drivers/fastboot/ |
| H A D | fb_getvar.c | 31 const char *variable; member
35 .variable = "version",
38 .variable = "bootloader-version",
41 .variable = "version-bootloader",
44 .variable = "downloadsize",
47 .variable = "max-download-size",
50 .variable = "serialno",
53 .variable = "version-baseband",
56 .variable = "product",
59 .variable = "current-slot",
[all …]
|
| /openbmc/openbmc/poky/bitbake/doc/bitbake-user-manual/ |
| H A D | bitbake-user-manual-metadata.rst | 19 Basic Variable Setting
22 The following example sets ``VARIABLE`` to "value". This assignment
26 VARIABLE = "value"
31 VARIABLE = " value"
32 VARIABLE = "value "
34 Setting ``VARIABLE`` to "" sets
35 it to an empty string, while setting the variable to " " sets it to a
38 VARIABLE = ""
39 VARIABLE = " "
42 variable's value. Doing so allows you to use values that contain the
[all …]
|
| H A D | bitbake-user-manual-ref-variables.rst | 23 systems extend the functionality of the variable as it is
42 This variable can be defined to be used by the fetcher to authenticate
58 considerations surrounding this variable:
98 the checksum mechanism. A common example would be the variable for
116 codeparser cache is used (i.e. when calculating variable dependencies for
133 ``mc1.conf`` would make this variable equal to ``mc1``).
149 variable, use the following form::
165 BB_DISKMON_WARNINTERVAL variable,
193 variable. This example causes the build system to immediately halt
196 directories are provided with the variable, the build system also
[all …]
|
| /openbmc/openbmc/poky/meta/conf/ |
| H A D | documentation.conf | 67 …n a recipe inherits the features_check class, at least one item in this variable must be included …
68 …n a recipe inherits the features_check class, at least one item in this variable must be included …
69 …n a recipe inherits the features_check class, at least one item in this variable must be included …
73 AUTOREV[doc] = "When SRCREV is set to the value of this variable, it specifies to use the latest so…
78 … not to install despite being recommended by a recipe. Support for this variable exists only when …
80 …ce and free inode warning intervals. To set these intervals, define the variable in the conf/local…
82 …ld run in parallel at any one time. A good rule of thumb is to set this variable to twice the numb…
85 BBFILE_PATTERN[doc] = "Variable that expands to match files from BBFILES in a particular layer. Thi…
86 BBFILE_PRIORITY[doc] = "Assigns the priority for recipe files in each layer. Setting this variable …
88 BBINCLUDELOGS[doc] = "Variable that controls how BitBake displays logs on build failure."
[all …]
|
| /openbmc/openbmc/poky/documentation/ref-manual/ |
| H A D | variables.rst | 53 To use the variable, list out the package's commands that are also
67 use the :term:`ALTERNATIVE_LINK_NAME` variable to specify the actual
85 duplicated commands. You can use the variable to create a single
101 duplicated commands. You can use the variable to create a single
114 from the :term:`ALTERNATIVE_LINK_NAME` variable.
130 class, this variable identifies a list of distribution features where
143 information on how this variable is used.
151 You can use this variable to create archives of patched source,
153 following variable flags (varflags)::
164 For information on how the variable works, see the
[all …]
|
| /openbmc/openbmc/poky/bitbake/bin/ |
| H A D | bitbake-getvar | 23 parser = argparse.ArgumentParser(description="Bitbake Query Variable")
24 parser.add_argument("variable", help="variable name to query")
27 …parser.add_argument('-f', '--flag', help='Specify a variable flag to query (with --value)', defaul…
28 …parser.add_argument('--value', help='Only report the value, no history and no variable name', acti…
56 value = d.getVarFlag(args.variable, args.flag, expand=not args.unexpand)
58 sys.exit(f"The flag '{args.flag}' is not defined for variable '{args.variable}'")
60 value = d.getVar(args.variable, expand=not args.unexpand)
62 sys.exit(f"The variable '{args.variable}' is not defined")
66 bb.data.emit_var(args.variable, d=d, all=True)
|
| /openbmc/qemu/qapi/ |
| H A D | uefi.json | 7 # UEFI Variable Store
10 # The QEMU efi variable store implementation (hw/uefi/) uses this to
21 # UEFI Variable. Check the UEFI specifification for more detailed
24 # @guid: variable namespace GUID
26 # @name: variable name, in UTF-8 encoding.
28 # @attr: variable attributes.
30 # @data: variable value, encoded as hex string.
32 # @time: variable modification time. EFI_TIME struct, encoded as hex
37 # @digest: variable certificate digest. Used to verify the signature
42 # of the signing certificate at variable creation time, and any
|
| /openbmc/qemu/include/qemu/ |
| H A D | coroutine-tls.h | 57 * optimizations that make assumptions about the address of the TLS variable.
66 * @type: the variable's C type
67 * @var: the variable name
69 * Declare an extern variable in Thread Local Storage from a header file:
72 * :caption: Declaring an extern variable in Thread Local Storage
84 * :caption: Declaring a TLS variable using __thread
99 * @type: the variable's C type
100 * @var: the variable name
102 * Define a variable in Thread Local Storage that was previously declared from
106 * :caption: Defining a variable in Thread Local Storage
[all …]
|
| /openbmc/u-boot/test/py/tests/ |
| H A D | test_env.py | 14 This enables quick determination of existant/non-existant variable
56 """Return the name of an environment variable that exists.
62 The name of an environment variable.
69 """Return the name of an environment variable that does not exist.
75 The name of an environment variable.
96 """Unset an environment variable.
103 var: The variable name to unset.
114 """Set an environment variable.
121 var: The variable name to set.
122 value: The value to set the variable to.
[all …]
|
| /openbmc/openbmc/poky/documentation/sdk-manual/ |
| H A D | appendix-customizing.rst | 43 are included. Including a variable in the value of
57 useful if you want to set a variable value just for the SDK and not the
68 :term:`INHERIT` variable and you
71 variable as described in the previous section.
99 variable as described in the previous section.
110 variable. For more information, see the
131 :term:`COREBASE_FILES` variable as previously described.
137 :term:`SDK_TITLE` variable and then
144 set. If the :term:`DISTRO_NAME` variable is not set, the title is derived
145 from the :term:`DISTRO` variable.
[all …]
|
| /openbmc/phosphor-pid-control/pid/ |
| H A D | tuning.hpp | 5 /** Boolean variable controlling whether tuning is enabled
10 /** String variable with the folder for writing logs if logging is enabled.
13 /** Boolean variable whether loggingPath is non-empty. */
16 /** Boolean variable controlling whether debug mode is enabled
21 /** Boolean variable enabling logging of computations made at the core of
|
| /openbmc/openbmc/poky/scripts/ |
| H A D | makefile-getvar | 3 # Get a variable's value from a makefile:
5 # $ makefile-getvar Makefile VARIABLE VARIABLE ...
17 for VARIABLE in $*; do
18 make -f - $VARIABLE.var <<EOF
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | customizing-images.rst | 17 variable changes are in effect for every build and consequently affect
21 the :term:`IMAGE_INSTALL` variable with the ``:append`` operator::
32 so unconditionally appends to the variable and avoids ordering problems
33 due to the variable being set in image recipes and ``.bbclass`` files
38 images. It is possible to extend the syntax so that the variable applies
46 :term:`CORE_IMAGE_EXTRA_INSTALL` variable. If you use this variable, only
68 variable and then maps or configures the feature accordingly. Based on
71 :term:`IMAGE_INSTALL` variable.
75 Use the :term:`EXTRA_IMAGE_FEATURES` variable from within your local
77 with this variable helps you avoid overwriting the features in the image
[all …]
|
| H A D | device-manager.rst | 25 :term:`USE_DEVFS` variable to "0"
33 variable defines the Device Table to use and should be set in the
35 variable in your ``local.conf`` configuration file.
37 If you do not define the :term:`IMAGE_DEVICE_TABLES` variable, the default
50 variable to "1", which is the default::
57 variable ``CONFIG_DEVTMPFS`` is set when building you build a Linux
65 :term:`VIRTUAL-RUNTIME_dev_manager <VIRTUAL-RUNTIME>` variable in your machine
66 or distro configuration file. Alternatively, you can set this variable in
|