| /openbmc/linux/fs/nls/ |
| H A D | Kconfig | 44 native language character sets. These character sets are stored
46 codepage if you want to be able to read/write these filenames on
56 native language character sets. These character sets are stored
58 codepage if you want to be able to read/write these filenames on
68 native language character sets. These character sets are stored
70 codepage if you want to be able to read/write these filenames on
81 native language character sets. These character sets are stored in
83 codepage if you want to be able to read/write these filenames on
97 native language character sets. These character sets are stored in
99 codepage if you want to be able to read/write these filenames on
[all …]
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| 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 | 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 | 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…
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-tty | 29 These sysfs values expose the TIOCGSERIAL interface via
38 These sysfs values expose the TIOCGSERIAL interface via
47 These sysfs values expose the TIOCGSERIAL interface via
56 These sysfs values expose the TIOCGSERIAL interface via
65 These sysfs values expose the TIOCGSERIAL interface via
74 These sysfs values expose the TIOCGSERIAL interface via
83 These sysfs values expose the TIOCGSERIAL interface via
92 These sysfs values expose the TIOCGSERIAL interface via
101 These sysfs values expose the TIOCGSERIAL interface via
110 These sysfs values expose the TIOCGSERIAL interface via
[all …]
|
| /openbmc/linux/Documentation/trace/coresight/ |
| H A D | coresight-perf.rst | 40 If you see these above, then your system is tracing CoreSight data
94 minimum level of functionality is met. The scripts that launch these
95 tests are in the same directory. These will all look like:
102 These perf record tests will not run if the tool binaries do not exist
105 CoreSight support or remove these binaries in order to not have these
108 These tests will log historical results in the current working
115 These statistic files log some aspects of the AUX data sections in
123 multiple times and all these csv files will have more and more data
127 This means sometimes these tests fail as they don't capture all the
132 Be aware that some of these tests take quite a while to run, specifically
[all …]
|
| /openbmc/linux/Documentation/ABI/ |
| H A D | README | 2 userspace, and the relative stability of these interfaces. Due to the
3 everchanging nature of Linux, and the differing maturity levels, these
14 defined to be stable. Userspace programs are free to use these
26 programs can start to rely on these interfaces, but they must be
27 aware of changes that can occur before these interfaces move to
28 be marked stable. Programs that use these interfaces are
30 these interfaces, so that the kernel developers can easily
44 Every file in these directories will contain the following information:
56 important to get feedback for these interfaces to make
|
| /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/linux/drivers/scsi/arm/ |
| H A D | Kconfig | 11 Acorn system with one of these, say Y. If unsure, say N.
40 Acorn system with one of these, say Y. If unsure, say N.
47 system with one of these, say Y, otherwise say N.
54 you have one of these, say Y. If unsure, say N.
65 Acorn system with one of these, say Y. If unsure, say N.
73 system with one of these, say Y. If unsure, say N.
|
| /openbmc/linux/include/linux/sunrpc/ |
| H A D | metrics.h | 11 * These statistics are not for detailed problem diagnosis, but simply
14 * These counters are not meant to be human-readable, but are meant to be
23 * arrays per-CPU because these counters are always modified behind locks.
39 * These counters give an idea about how many request
51 * These count how many bytes are sent and received for a
53 * particular procedure is putting on the network. These
71 * These statuses usually indicate error conditions.
|
| /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/linux/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/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/linux/tools/memory-model/Documentation/ |
| H A D | ordering.txt | 15 2. Ordered memory accesses. These operations order themselves
23 some of these "unordered" operations provide limited ordering
46 Note well that many of these primitives generate absolutely no code
82 Second, some RMW atomic operations provide full ordering. These
113 Finally, RCU's grace-period primitives provide full ordering. These
115 synchronize_srcu() and so on. However, these primitives have orders
132 full ordering for these primitives. One way to obtain full ordering on
263 end in _release. These operations order their own store against all
321 and value-returning RMW operations whose names end in _acquire. These
441 Each of these two categories of unordered accesses has a section below:
[all …]
|
| /openbmc/linux/arch/xtensa/include/uapi/asm/ |
| H A D | mman.h | 19 * Protections are chosen from these bits, OR'd together. The
47 /* These are linux-specific */
84 #define MADV_WILLNEED 3 /* will need these pages */
85 #define MADV_DONTNEED 4 /* don't need these pages */
87 /* common parameters: try to keep these consistent across architectures */
89 #define MADV_REMOVE 9 /* remove these pages & resources */
106 #define MADV_COLD 20 /* deactivate these pages */
107 #define MADV_PAGEOUT 21 /* reclaim these pages */
|
| /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/linux/arch/mips/include/uapi/asm/ |
| 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/linux/Documentation/devicetree/bindings/sifive/ |
| H A D | sifive-blocks-ip-versioning.txt | 4 strings for open-source SiFive IP blocks. HDL for these IP blocks
16 Until these IP blocks (or IP integration) support version
17 auto-discovery, the maintainers of these IP blocks intend to increment
19 interface to these IP blocks changes, or when the functionality of the
26 match on these IP block-specific compatible strings.
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | device-io.rst | 54 historical accident, these are named byte, word, long and quad accesses.
63 8 bytes at a time. For these devices, the memcpy_toio(),
112 these cases, although only some platforms will honor the relaxed
126 addresses separate to the normal memory address space. Access to these
138 long. These functions are inb(), inw(),
142 Some variants are provided for these functions. Some devices require
171 These are the most generic accessors, providing serialization against other
174 should generally use these for any access to ``__iomem`` pointers.
183 DMA, these "relaxed" versions of the MMIO accessors only serialize against
185 might use these in a particularly performance sensitive fast path, with a
[all …]
|
| /openbmc/linux/Documentation/ABI/stable/ |
| H A D | sysfs-driver-mlxreg-io | 15 Description: These files show with which CPLD versions have been burned
34 Description: These files show with which CPLD versions have been burned
43 Description: These files enable and disable the access to the JTAG domain.
66 Description: These files allow asserting system power cycling, switching
93 Description: These files show the system reset cause, as following: power
110 Description: These files show the system reset cause, as following: ComEx
123 Description: These files show with which CPLD versions have been burned
137 Description: These files show the system reset cause, as following:
152 Description: These files show system static topology identification
165 Description: These files show the system reset causes, as following: reset
[all …]
|
| /openbmc/linux/Documentation/security/ |
| H A D | self-protection.rst | 26 is uncommon that all these goals can be met, but it is worth explicitly
27 mentioning them, since these aspects need to be explored, dealt with,
44 to redirect execution flow. To reduce the availability of these targets
54 alternatives, breakpoints, kprobes, etc. If these must exist in a
64 Most architectures have these options on by default and not user selectable.
65 For some architectures like arm that wish to have these be selectable,
75 tables, file/network/etc operation structures, etc). The number of these
83 For variables that are initialized once at ``__init`` time, these can
86 What remains are variables that are updated rarely (e.g. GDT). These
97 access userspace memory without explicit expectation to do so. These
[all …]
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | abi-testing.rst | 11 Userspace programs can start to rely on these interfaces, but they must
12 be aware of changes that can occur before these interfaces move to
15 Programs that use these interfaces are strongly encouraged to add their
16 name to the description of these interfaces, so that the kernel
|
| /openbmc/openbmc/poky/documentation/test-manual/ |
| H A D | intro.rst | 102 :ref:`ref-classes-insane` class. These checks ensure the output of the
110 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 …]
|