| /OK3568_Linux_fs/yocto/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 …]
|
| /OK3568_Linux_fs/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 | 54 Environment variables
66 1. Setup tftp env variables:
69 * setup "serverip" and "ipaddr" variables
82 2. Setup update_tftp variables:
89 4. Inspect "dfu" specific variables:
|
| /OK3568_Linux_fs/yocto/poky/bitbake/bin/ |
| H A D | toaster-eventreplay | 37 def __init__(self, eventfile, variables): argument
39 self.variables = variables
64 variable = self.variables.get(var_name)
72 for key, val in self.variables.items():
102 variables = json.loads(eventfile.readline().strip())['allvariables']
105 player = EventPlayer(eventfile, variables)
|
| /OK3568_Linux_fs/kernel/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)
|
| /OK3568_Linux_fs/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
|
| /OK3568_Linux_fs/yocto/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."
|
| /OK3568_Linux_fs/kernel/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:
|
| /OK3568_Linux_fs/yocto/poky/meta/lib/oeqa/utils/ |
| H A D | commands.py | 241 def get_bb_vars(variables=None, target=None, postconfig=None): argument
245 if variables is not None:
246 variables = list(variables)
264 if variables is None:
267 if var in variables:
269 variables.remove(var)
271 if not variables:
274 if variables:
276 for var in variables:
|
| /OK3568_Linux_fs/yocto/poky/bitbake/lib/bb/ |
| H A D | data_smart.py | 234 self.variables = COWDictBase.copy()
238 new.variables = self.variables.copy()
243 for k, v in self.variables.iteritems():
250 self.variables = COWDictBase.copy()
252 self.variables[k] = v
270 if var not in self.variables:
271 self.variables[var] = []
272 if not isinstance(self.variables[var], list):
274 if 'nodups' in loginfo and loginfo in self.variables[var]:
276 self.variables[var].append(loginfo.copy())
[all …]
|
| /OK3568_Linux_fs/kernel/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
170 shadow variables to parents already in-flight.
208 Shadow variables can also be used as a flag indicating that a data
220 variables.
|
| /OK3568_Linux_fs/buildroot/package/pkgconf/ |
| H A D | 0001-Only-prefix-with-the-sysroot-a-subset-of-variables.patch | 4 Subject: [PATCH] Only prefix with the sysroot a subset of variables
19 pkgdatadir and sdkdir. This list of variables was collected over years of
91 - * :param pkgconf_list_t* list: The variable list to search for variables (along side the globa…
93 - * :return: the variable data with any variables substituted
131 + * :param pkgconf_list_t* list: The variable list to search for variables (along side the globa…
133 + * :return: the variable data with any variables substituted
|
| /OK3568_Linux_fs/yocto/poky/documentation/sdk-manual/ |
| H A D | working-projects.rst | 136 To learn about environment variables established when you run the
161 environment variables established when you run the cross-toolchain
162 environment setup script. The environment variables are subject to
167 variables and Makefile variables during development.
177 variables are not specifically set in the ``Makefile``, the variables
182 setting matching variables in the ``Makefile`` during the build
183 results in the environment settings of the variables being
184 overwritten. In this case, the variables you set in the ``Makefile``
190 environment variables being overwritten. In this case, the
195 Regardless of how you set your variables, if you use the "-e" option
[all …]
|
| /OK3568_Linux_fs/buildroot/docs/manual/ |
| H A D | make-tips.txt | 81 .Dumping the internal make variables:
83 One can dump the variables known to make, along with their values:
91 It is possible to tweak the output using some variables:
93 - +VARS+ will limit the listing to variables which names match the
127 The output of quoted variables can be reused in shell scripts, for example:
|
| H A D | adding-packages-meson.txt | 43 The Makefile starts with the definition of the standard variables for package
66 variables.
77 a number of variables before calling the +meson-package+ macro.
79 First, all the package metadata information variables that exist in the generic
84 A few additional variables, specific to the Meson infrastructure, can also be
94 * +FOO_CONF_ENV+, to specify additional environment variables to pass to
128 * +FOO_NINJA_ENV+, to specify additional environment variables to pass to
|
| H A D | adding-packages-qmake.txt | 51 by defining a number of variables before calling the +qmake-package+
54 First, all the package metadata information variables that exist in
63 * +LIBFOO_CONF_ENV+, to specify additional environment variables to
69 * +LIBFOO_MAKE_ENV+, to specify additional environment variables to the
|
| H A D | adding-packages-rebar.txt | 51 by defining a number of variables before calling the +rebar-package+
54 First, all the package metadata information variables that exist in
62 A few additional variables, specific to the +rebar+ infrastructure,
71 You can also use some of the variables from the +autotools+
87 variables to pass to the _rebar_ utility.
|
| /OK3568_Linux_fs/kernel/security/ |
| H A D | Kconfig.hardening | 13 such variables, depending on the chosen level of coverage.
38 prompt "Initialize kernel stack variables at function entry"
44 This option enables initialization of stack variables at
47 variables initialized), but the performance impact depends
52 uninitialized variables. The selected class of variable will be
87 As a side-effect, this keeps a lot of variables on the
98 Zero-initialize any stack variables that may be passed
104 As a side-effect, this keeps a lot of variables on the
116 information exposures, even variables that were warned about
134 information exposures, even variables that were warned
[all …]
|
| /OK3568_Linux_fs/kernel/tools/bpf/bpftool/Documentation/ |
| H A D | bpftool-gen.rst | 35 structure by listing out available maps, program, variables,
57 global variables of all supported kinds: mutable, read-only,
59 initial values of variables before BPF object is loaded and
60 verified by kernel. For non-read-only variables, the same
61 interface can be used to fetch values of global variables on
113 If BPF object has global variables, corresponding structs
118 values of variables, if set before **example__load**.
173 and global variables.
|
| /OK3568_Linux_fs/kernel/Documentation/trace/ |
| H A D | histogram-design.rst | 76 histogram val and key in the histogram (variables are also included
370 In terms of the histogram data structures, variables are implemented
569 .vars containing the current value of the variables associated with | |
703 event_name variables are also set.
736 location. Note also that the output shows that variables live in the
784 variables and values, they actually live in a separate hist_data
867 variables specified in the wakeup_latency() trace action, and use
873 variables. In this case, $wakeup_lat is obviously a variable, but
912 the linkages between the field_vars and the variables and references
913 created to implement the field variables. The details are discussed
[all …]
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-extended/minicom/minicom/ |
| H A D | 0002-Drop-superfluous-global-variable-definitions.patch | 7 global variables 'vt_outmap' and 'vt_inmap' is minicom.c (by defining
9 vt100.c already defines these variables. The vt100.o object file is
11 variables in minicom.c and only declare them in the minicom.h header.
|
| /OK3568_Linux_fs/kernel/Documentation/core-api/ |
| H A D | local_ops.rst | 14 those local variables across CPUs when the order of memory writes matters.
66 * Variables touched by local ops must be per cpu variables.
67 * *Only* the CPU owner of these variables must write to them.
69 to update its ``local_t`` variables.
81 * Reads of these variables can be done from any CPU, because updates to
82 "``long``", aligned, variables are always atomic. Since no memory
84 variable can be read when reading some *other* cpu's variables.
|
| /OK3568_Linux_fs/yocto/poky/bitbake/doc/bitbake-user-manual/ |
| 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 …]
|