| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | Elastic-2.0 | 39 the software granted under these terms ends immediately. If your company makes
46 also gets a copy of these terms.
53 These terms do not imply any licenses other than those expressly granted in
54 these terms.
58 If you use the software in violation of these terms, such use is not licensed,
62 reinstated retroactively. However, if you violate these terms after such
63 reinstatement, any additional violation of these terms will cause your licenses
70 out of these terms or the use or nature of the software, under any kind of
75 The **licensor** is the entity offering these terms, and the **software** is the
76 software the licensor makes available under these terms, including any portion
[all …]
|
| H A D | PolyForm-Noncommercial-1.0.0 | 7 In order to get any license under these terms, you must agree
33 the software from you also gets a copy of these terms or the
76 law. These terms do not limit them.
80 These terms do not allow you to sublicense or transfer any of
82 granting licenses to anyone else. These terms do not imply
89 for the software granted under these terms ends immediately. If
96 violated any of these terms, or done anything with the software
98 continue if you come into full compliance with these terms,
107 to you for any damages arising out of these terms or the use
112 The **licensor** is the individual or entity offering these
[all …]
|
| H A D | PolyForm-Small-Business-1.0.0 | 7 In order to get any license under these terms, you must agree
33 the software from you also gets a copy of these terms or the
55 law. These terms do not limit them.
70 These terms do not allow you to sublicense or transfer any of
72 granting licenses to anyone else. These terms do not imply
79 for the software granted under these terms ends immediately. If
86 violated any of these terms, or done anything with the software
88 continue if you come into full compliance with these terms,
97 to you for any damages arising out of these terms or the use
102 The **licensor** is the individual or entity offering these
[all …]
|
| H A D | ASWF-Digital-Assets-1.0 | 7 Redistribution and use of these digital assets, with or without modification, solely for education,…
9 1. Redistributions of these digital assets or any part of them must include the above copyright not…
11 2. Publications showing images derived from these digital assets must include the above copyright n…
13 …with products developed or tested utilizing these digital assets or benchmarking results obtained …
17 …THESE DIGITAL ASSETS ARE PROVIDED BY THE COPYRIGHT HOLDER "AS IS" AND ANY EXPRESS OR IMPLIED WARRA…
|
| H A D | ASWF-Digital-Assets-1.1 | 7 Redistribution and use of these digital assets, with or without modification, solely for education,…
9 1. Redistributions of these digital assets or any part of them must include the above copyright not…
11 2. Publications showing images derived from these digital assets must include the above copyright n…
13 …with products developed or tested utilizing these digital assets or benchmarking results obtained …
17 …THESE DIGITAL ASSETS ARE PROVIDED BY THE COPYRIGHT HOLDER "AS IS" AND ANY EXPRESS OR IMPLIED WARRA…
|
| H A D | MPEG-SSG | 5 These software programs are available to the user without any license fee or
11 arising from the use of these programs.
13 This disclaimer of warranty extends to the user of these programs and user's
21 are subject to royalty fees to patent holders. Many of these patents are
|
| H A D | Bahyph | 3 These patterns and the generating sh script are Copyright (c) GMV 1991
5 These patterns were developed for internal GMV use and are made public in the hope that they will b…
7 …s, you responsible for repair. Use of this software is an explicit acceptance of these conditions.
|
| /openbmc/docs/architecture/ |
| H A D | optionality.md | 11 Linux kernel, systemd, sdbusplus, and phosphor object mapper. These features are
16 These are subsystems that, while widely applicable, a user might choose to
19 image, or might be done to reduce the security attack surface. These kids of
21 functional impacts to other subsystems. Examples of these include the webui,
27 one of these categories. For non-trivial feature additions, the commit message
35 therefore don't need to be able to be configured. Examples of these would
37 limits, and required commands. These types of features generally show no
70 Specific mechanisms to enable or disable these features are commonly:
|
| /openbmc/u-boot/fs/jffs2/ |
| H A D | LICENCE | 21 macros or inline functions from these files, or you compile these
22 files and link them with other works to produce a work based on these
23 files, these files do not by themselves cause the resulting work to be
25 these files must still be made available in accordance with section (3)
|
| /openbmc/docs/designs/oem/ibm/ |
| H A D | system-power-mode.md | 33 the OCC state changes to ACTIVE or the customer updates these new parameters at
75 parameters. These commands are defined in the OCC Interface Spec:
79 parameters for the system. If the customer has not yet set any of these
80 parameters, these default values will be used. If/when the customer does set any
81 of these, that new customer parameter will become current and the default value
86 xyz/openbmc_project/Control/Power/Mode.interface.yaml Once set, these values
100 Security impact - update of these parameters should be able to be restricted to
101 specific users/groups (may not want any user updating these parameters)
|
| /openbmc/qemu/linux-headers/asm-mips/ |
| H A D | mman.h | 13 * Protections are chosen from these bits, OR'd together. The
40 /* These are linux-specific */
75 #define MADV_WILLNEED 3 /* will need these pages */
76 #define MADV_DONTNEED 4 /* don't need these pages */
78 /* common parameters: try to keep these consistent across architectures */
80 #define MADV_REMOVE 9 /* remove these pages & resources */
98 #define MADV_COLD 20 /* deactivate these pages */
99 #define MADV_PAGEOUT 21 /* reclaim these pages */
|
| /openbmc/openbmc/poky/meta/classes/ |
| H A D | distrooverrides.bbclass | 8 # name plus a df- prefix. Ensures that these special
10 # recipes, so that these overrides can also be used there.
24 # of these overrides should be limited to .bb and .bbappend files,
36 # OVERRIDES itself should be fixed. Excluding these two variables
|
| /openbmc/qemu/linux-headers/asm-generic/ |
| H A D | mman-common.h | 48 #define MADV_WILLNEED 3 /* will need these pages */
49 #define MADV_DONTNEED 4 /* don't need these pages */
51 /* common parameters: try to keep these consistent across architectures */
53 #define MADV_REMOVE 9 /* remove these pages & resources */
72 #define MADV_COLD 20 /* deactivate these pages */
73 #define MADV_PAGEOUT 21 /* reclaim these pages */
|
| H A D | hugetlb_encode.h | 6 * Without further specification, these system calls will use the
9 * bits [26:31] of the flag arguments. The value in these 6 bits
15 * provide definitions based on these with their own specific prefix.
|
| /openbmc/u-boot/doc/device-tree-bindings/ |
| H A D | README | 6 These follow along with Linux kernel bindings, with a few additions. By
8 This makes it easier for device tree people to review these additions in
11 The intent IS to commit these files to U-Boot. Hopefully at some point
|
| /openbmc/docs/designs/mctp/ |
| H A D | mctp.md | 22 allows us to design these parts separately. Currently, IPMI defines both of
23 these; we currently have BT and KCS (both defined as part of the IPMI 2.0
31 layer bindings for the actual transport of MCTP packets. These are defined by
36 The following diagram shows how these standards map to the areas of
45 stack needing to be aware of the hardware implementation. These higher levels
47 by an Entity ID (MCTP EID). These entities may be any element of the platform
119 users of the MCTP messaging (eg, a PLDM implementation). These would somewhat
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | read-only-rootfs.rst | 36 For more information on how to use these variables, see the
48 the build on the host system. These scripts cannot attempt to run during
51 succeed at file system creation time. If any of these scripts
53 immediately fails. These build-time checks ensure that the build fails
75 target architecture:* You can work around these attempts by using
87 these types of writes do so to directories with write access (e.g.
|
| /openbmc/u-boot/doc/driver-model/ |
| H A D | serial-howto.txt | 4 Almost all of the serial drivers have been converted as at January 2016. These
11 forward to convert these, at some point there may come a patch to remove them!
29 In terms of patches a conversion series typically has these patches:
36 this involves these steps:
|
| H A D | i2c-howto.txt | 4 Over half of the I2C drivers have been converted as at November 2016. These
21 forward to convert these, at some point there may come a patch to remove them!
39 In terms of patches a conversion series typically has these patches:
46 this involves these steps:
|
| /openbmc/openbmc/meta-openembedded/meta-gnome/recipes-connectivity/geary/geary/ |
| H A D | 0001-meson-Do-not-check-for-iso-xml-files-during-build.patch | 6 These files are needed during runtime and may exist in a different
8 valid to check for these files to exist during build-time
24 -files(iso_639_xml, iso_3166_xml) # Check to make sure these exist
|
| /openbmc/qemu/docs/devel/ |
| H A D | loads-stores.rst | 19 These functions operate on a host pointer, and should be used
76 These functions operate on a guest virtual address, plus a context
87 These functions may cause a guest CPU exception to be taken
131 These functions work like the ``cpu_{ld,st}_mmu`` functions except
164 These functions work like the ``cpu_{ld,st}_mmuidx_ra`` functions
168 These are generally the preferred way to do accesses by guest
202 These functions work like the ``cpu_{ld,st}_data_ra`` functions
207 translator has saved all necessary CPU state. These functions are
241 These functions perform a read for instruction execution. The ``mmuidx``
249 In general these functions should not be used directly during translation.
[all …]
|
| /openbmc/openbmc/poky/documentation/test-manual/ |
| H A D | intro.rst | 100 :ref:`ref-classes-insane` class. These checks ensure the output of the
108 These tests are run on isolated machines so that the time
171 These tests are self-contained and test BitBake as well as its APIs,
175 Some of these tests run the ``bitbake`` command, so ``bitbake/bin``
213 - These tests use OE to test the workflows, which include testing
250 - These tests build an image, boot it, and run tests against the
253 - The code for these tests resides in ``meta/lib/oeqa/runtime/cases/``.
265 - These tests build an SDK, install it, and then run tests against
268 - The code for these tests resides in ``meta/lib/oeqa/sdk/cases/``.
276 - These tests build an extended SDK (eSDK), install that eSDK, and
[all …]
|
| /openbmc/qemu/python/ |
| H A D | README.rst | 12 1. ``pip3 install .`` will install these packages to your current
17 2. ``pip3 install --user .`` will install these packages to your user's
29 and are not needed to simply use these libraries.
40 Using these packages without installing them
43 These packages may be used without installing them first, by using one
|
| /openbmc/u-boot/doc/ |
| H A D | README.fsl-trustzone-components | 5 While most of the configuration related programming of these peripherals
7 privilege mode), but still some configurations of these peripherals
9 mode. The following sections define how to turn on these features for
|
| /openbmc/phosphor-pid-control/dbus/ |
| H A D | README | 3 These sensors wait for their updates.
7 These sensors reach out for their value.
|