| /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.
37 BitBake during the build of a particular recipe. Those variables are
42 handled. Those are usually set by ``bitbake.conf`` and might get adapted in a
47 :term:`PERSISTENT_DIR`. Those are usually global.
63 Those variables are often used in the files ``layer.conf`` and ``bblayers.conf``.
72 ``bitbake.conf`` is used, but those are from time to time overwritten in
85 a recipe like :term:`SRC_URI` or :term:`SRCDATE`. Those are also usually set
90 starting with ``PREFERRED_``. Those are normally set in the configuration
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | NRL | 7 …those portions are copyright by The Regents of the University of California. All Rights Reserved. …
9 …Those developers have each copyrighted the portions that they developed at NRL and have assigned A…
28 The views and conclusions contained in the software and documentation are those of the authors and …
|
| H A D | Community-Spec-1.0 | 17 it submits to the full extent of its copyright interest in those
41 Licensee’s Implementation of the Draft Specification, except for those
49 Specification, except for those patent claims excluded by Contributor
55 license to its Necessary Claims for its Implementation, except for those
95 applies only to those Necessary Claims infringed by implementing
99 This patent licensing commitment does not apply to those claims subject
162 any third party materials in any Contribution unless those materials are
244 is not set forth in the Exclusion Notice, those Necessary Claims shall
265 9.11. Necessary Claims. “Necessary Claims” are those patent claims, if
266 any, that a party owns or controls, including those claims later acquired,
|
| H A D | FDK-AAC | 16 Patent licenses for necessary patent claims for the FDK AAC Codec (including those of Fraunhofer)
21 software may already be covered under those patent licenses when it is used for those licensed purp…
|
| H A D | TAPR-OHL-1.0 | 21 rights under the OHL to deny any other licensee those same rights to
29 play a significant role in those activities. Although it does not prohibit
32 those who benefit from an OHL design may not bring lawsuits claiming that
58 * Include those modifications, following the requirements stated
187 You may modify the Documentation, and those modifications will become
205 file identifying those elements of the Documentation that you
|
| H A D | BSD-2-Clause-Patent | 14 and contributor hereby grants to those receiving rights under this license
18 this software, where such license applies only to those patent claims, already
|
| H A D | GPL-3.0-or-later | 55 the practice for those products. If such problems arise substantially in other
56 domains, we stand ready to extend this provision to those domains in future
61 computers, but in those that do, we wish to avoid the special danger that
131 code and to modify the work, including scripts to control those activities.
134 those activities but which are not part of the work. For example, Corresponding
138 intimate data communication or control flow between those subprograms and
159 exclusively for you, or provide you with facilities for running those works,
161 for which you do not control copyright. Those thus making or running the covered
321 may be used separately under those permissions, but the entire Program remains
355 assumptions directly impose on those licensors and authors.
[all …]
|
| H A D | GPL-3.0-only | 24 …the practice for those products. If such problems arise substantially in other domains, we stand r…
26 …rict development and use of software on general-purpose computers, but in those that do, we wish t…
55 …those activities. However, it does not include the work's System Libraries, or general-purpose too…
64 …nning those works, provided that you comply with the terms of this License in conveying all materi…
110 …apply only to part of the Program, that part may be used separately under those permissions, but t…
121 …, for any liability that these contractual assumptions directly impose on those licensors and auth…
125 … relevant source files, a statement of the additional terms that apply to those files, or a notice…
161 …tion with copies of the covered work conveyed by you (or copies made from those copies), or (b) pr…
166 …a royalty for further conveying from those to whom you convey the Program, the only way you could …
|
| H A D | SSPL-1.0 | 74 those activities. However, it does not include the work's System
76 which are used unmodified in performing those activities but which are
81 data communication or control flow between those subprograms and other
102 for you, or provide you with facilities for running those works, provided
104 material for which you do not control copyright. Those thus making or
280 to part of the Program, that part may be used separately under those
314 liability that these contractual assumptions directly impose on those
329 that apply to those files, or a notice indicating where to find the
456 those copies), or (b) primarily for and in connection with specific
474 further conveying from those to whom you convey the Program, the only way
[all …]
|
| /openbmc/u-boot/arch/ |
| H A D | Kconfig | 187 This is optional. For those targets without the CPU directory,
196 This is optional. For those targets without the SoC directory,
209 This is optional. For those targets without the vendor directory,
220 This is optional. For those targets without the board directory,
|
| /openbmc/u-boot/doc/device-tree-bindings/pinctrl/ |
| H A D | pinctrl-bindings.txt | 17 states. The number and names of those states is defined by the client device's
21 for client device device tree nodes to map those state names to the pin
22 configuration used by those states.
39 those names to the integer IDs.
120 The contents of each of those pin configuration child nodes is defined
220 Some of the generic properties take arguments. For those that do, the
|
| /openbmc/qemu/docs/tools/ |
| H A D | qemu-vmsr-helper.rst | 20 However those registers are accessible under privileged access (CAP_SYS_RAWIO).
21 QEMU can use an external helper to access those privileged registers.
32 optionally drop root privileges, except for those capabilities that
|
| /openbmc/openbmc/meta-openembedded/meta-perl/recipes-perl/libmodule/ |
| H A D | libmodule-pluggable-perl_5.2.bb | 7 looks through a search path for .pm files and turn those into class \
10 Optionally it instantiates those classes for you."
|
| /openbmc/openbmc/meta-arm/ci/ |
| H A D | jobs-to-kas | 28 # Given that there are no yml files for gcc or glibc, as those are the
29 # defaults, we can simply ignore those parameters. They are necessary
|
| /openbmc/u-boot/env/ |
| H A D | nvram.c | 15 * the memory space. (I.e. this is the case for the BAB750). In those
19 * NVRAM in those cases I invented the functions 'nvram_read()' and
21 * #define CONFIG_SYS_NVRAM_ACCESS_ROUTINE. Note, that those functions are
|
| /openbmc/openbmc/meta-openembedded/meta-multimedia/licenses/ |
| H A D | Fraunhofer_FDK_AAC_Codec_Library_for_Android | 19 those of Fraunhofer) may be obtained through Via Licensing
25 already be covered under those patent licenses when it is used for those
|
| /openbmc/openbmc/meta-openembedded/meta-oe/licenses/ |
| H A D | zsh | 6 binary including those files needs to take account of this. Search
8 None of the core functions are affected by this, so those files may
|
| /openbmc/u-boot/include/linux/ |
| H A D | libfdt.h | 93 * the regions of the device tree which describe those included parts.
96 * those parts are invariant. For example, if you request a list of regions
105 * or subnodes of those subnodes).
121 * being extended (if the new property names are different from those
152 * the regions of the device tree which describe those included parts.
165 * those parts are invariant. For example, if you request a list of regions
217 * being extended (if the new property names are different from those
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-core/packagegroups/ |
| H A D | packagegroup-basic.bb | 35 # 1) Machine features: kernel modules and userspace helpers for those
36 # 2) Distro features: packages associated with those
|
| /openbmc/qemu/docs/devel/testing/ |
| H A D | ci-runners.rst.inc | 36 those hosts. This would look like::
58 privileges, such as those from the ``root`` account or those obtained
|
| /openbmc/openbmc/poky/scripts/lib/devtool/ |
| H A D | import.py | 49 # will be needed to find out those appends without corresponding
65 # Find those appends that do not have recipes in current metadata
68 # Check on current metadata (covering those layers indicated in bblayers.conf)
|
| /openbmc/ipmi-fru-parser/ |
| H A D | LICENSE | 56 have designed this version of the GPL to prohibit the practice for those
58 stand ready to extend this provision to those domains in future versions
63 software on general-purpose computers, but in those that do, we wish to
137 control those activities. However, it does not include the work's
139 programs which are used unmodified in performing those activities but
144 such as by intimate data communication or control flow between those
168 with facilities for running those works, provided that you comply with
170 not control copyright. Those thus making or running the covered works
351 under those permissions, but the entire Program remains governed by
386 those licensors and authors.
[all …]
|
| /openbmc/openbmc/meta-arm/meta-arm/recipes-bsp/scp-firmware/files/ |
| H A D | 0001-OPTEE-Private-Includes.patch | 23 # Those includes are needed for mutex definitnion that is used in optee_smt
36 # Those includes are needed for mutex defifitnion that is used in optee_smt
|
| /openbmc/qemu/include/qemu/ |
| H A D | atomic128.h | 55 * The guest may issue a large atomic operation and then access those
57 * way to connect those two actions.
|
| /openbmc/phosphor-power/phosphor-regulators/docs/ |
| H A D | README.md | 9 monitor their Power Good (pgood) status. Those operations are typically
56 - Operations to perform on those regulators, such as configuration or sensor
|