| /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.
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
79 **you** refers to the individual or entity agreeing to these terms.
[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
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
114 available under these terms.
116 **You** refers to the individual or entity agreeing to these
128 software under these terms.
|
| 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
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
104 available under these terms.
106 **You** refers to the individual or entity agreeing to these
118 software under these terms.
|
| 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 …
|
| 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 …
|
| H A D | MPEG-SSG | 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
|
| /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/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/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/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/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/virt/kvm/x86/ |
| H A D | errata.rst | 27 Clearing these bits in CPUID has no effect on the operation of the guest;
28 if these bits are set on hardware, the features will not be present on
31 **Workaround:** It is recommended to always set these bits in guest CPUID.
32 Note however that any software (e.g ``WIN87EM.DLL``) expecting these features
33 to be present likely predates these CPUID feature bits, and therefore
|
| /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/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
105 CoreSight support or remove these binaries in order to not have these
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
136 You can change where these csv logs are stored by setting the
156 You may wish to set these above environment variables if you wish to
|
| /openbmc/linux/Documentation/arch/arm/omap/ |
| H A D | omap_pm.rst | 6 authors use these functions to communicate minimum latency or
24 DaVinci) to add these constraints in a way which won't affect non-OMAP
71 As the 'pdata' in the above examples indicates, these functions are
78 not support these functions should leave these function pointers set
84 The most common usage of these functions will probably be to specify
120 frequency. The OMAP PM interface contains functions for these
148 in these cases, the board file needs to do additional steps as follows:
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | vidioc-dbg-g-register.rst | 43 For driver debugging purposes these ioctls allow test applications to
50 with the ``CONFIG_VIDEO_ADV_DEBUG`` option to enable these ioctls.
75 when a driver supports these ioctls it must also support
77 it may support ``VIDIOC_DBG_G_CHIP_INFO`` but not these ioctls.
83 We recommended the v4l2-dbg utility over calling these ioctls directly.
160 these ioctls.
|
| /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/linux/fs/nls/ |
| H A D | Kconfig | 46 codepage if you want to be able to read/write these filenames on
58 codepage if you want to be able to read/write these filenames on
70 codepage if you want to be able to read/write these filenames on
83 codepage if you want to be able to read/write these filenames on
99 codepage if you want to be able to read/write these filenames on
104 characters for these languages: Albanian, Croatian, Czech, English,
114 codepage if you want to be able to read/write these filenames on
125 codepage if you want to be able to read/write these filenames on
136 codepage if you want to be able to read/write these filenames on
147 codepage if you want to be able to read/write these filenames on
[all …]
|
| /openbmc/linux/arch/mips/jazz/ |
| H A D | Kconfig | 8 kernel that runs on these, say Y here. For details about Linux on
19 kernel that runs on these, say Y here. For details about Linux on
29 kernel that runs on these, say Y here. For details about Linux on
|
| /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
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/openbmc/meta-openembedded/meta-oe/recipes-extended/linuxconsole/ |
| H A D | linuxconsole_1.7.1.bb | 16 file://51-these-are-not-joysticks-rm.rules \
53 …install -Dm 0644 ${UNPACKDIR}/51-these-are-not-joysticks-rm.rules ${D}${nonarch_base_libdir}/udev/…
79 ${nonarch_base_libdir}/udev/rules.d/51-these-are-not-joysticks-rm.rules \
|
| /openbmc/linux/Documentation/admin-guide/sysctl/ |
| H A D | user.rst | 18 The primary purpose of these limits is to stop programs that
21 intention that the defaults of these limits are set high enough that
22 no program in normal operation should run into these limits.
36 Currently, these files are in /proc/sys/user:
|
| /openbmc/phosphor-pid-control/ |
| H A D | ipmi.md | 11 then write values to these virtual sensors, to keep them up to date. Thus, these
16 mentioned above, these can be manipulated through normal IPMI commands, and are
18 OEM commands are required to use these.
|
| /openbmc/linux/Documentation/admin-guide/perf/ |
| H A D | qcom_l3_pmu.rst | 6 Centriq SoCs. The L3 cache on these SOCs is composed of multiple slices, shared
12 options in sysfs, see /sys/devices/l3cache*. Given that these are uncore PMUs
25 Given that these are uncore PMUs the driver does not support sampling, therefore
|