| /OK3568_Linux_fs/yocto/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
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.
|
| /OK3568_Linux_fs/kernel/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
|
| /OK3568_Linux_fs/kernel/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
|
| /OK3568_Linux_fs/kernel/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)
|
| /OK3568_Linux_fs/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)
|
| /OK3568_Linux_fs/kernel/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.
|
| /OK3568_Linux_fs/kernel/drivers/scsi/arm/ |
| H A D | Kconfig | 11 Acorn system with one of these, say Y. If unsure, say N.
51 Acorn system with one of these, say Y. If unsure, say N.
58 system with one of these, say Y, otherwise say N.
65 you have one of these, say Y. If unsure, say N.
76 Acorn system with one of these, say Y. If unsure, say N.
84 system with one of these, say Y. If unsure, say N.
|
| /OK3568_Linux_fs/external/chromium/licenses/ |
| H A D | LICENSE.89 | 40 run, modify and propagate the contents of these implementations of WebM, where
43 infringed by these implementations of WebM. This grant does not include claims
44 that would be infringed only as a consequence of further modification of these
48 counterclaim in a lawsuit) alleging that any of these implementations of WebM
49 or any code incorporated within any of these implementations of WebM
52 for these implementations of WebM shall terminate as of the date such
|
| /OK3568_Linux_fs/kernel/Documentation/x86/ |
| H A D | intel-iommu.rst | 30 PS2 emulation. The regions of memory used for these devices are marked
32 regions will fail. Hence BIOS uses RMRR to specify these regions along with
33 devices that need to access these regions. OS is expected to setup
34 unity mappings for these regions for these devices to access these regions.
49 but these are not global address spaces, but separate for each domain.
|
| /OK3568_Linux_fs/yocto/poky/meta/classes/ |
| H A D | distrooverrides.bbclass | 2 # name plus a df- prefix. Ensures that these special
4 # recipes, so that these overrides can also be used there.
18 # of these overrides should be limited to .bb and .bbappend files,
30 # OVERRIDES itself should be fixed. Excluding these two variables
|
| /OK3568_Linux_fs/kernel/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 …]
|
| /OK3568_Linux_fs/kernel/Documentation/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:
|
| /OK3568_Linux_fs/kernel/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.
|
| /OK3568_Linux_fs/buildroot/package/hostapd/ |
| H A D | 0002-ASN.1-Validate-DigestAlgorithmIdentifier-parameters.patch | 9 not check the parameters value at all which supported both these cases,
54 + * omit the parameters, but there are implementation that encode these
55 + * as a NULL element. Allow these two cases and reject anything else.
99 + * omit the parameters, but there are implementation that encode these
100 + * as a NULL element. Allow these two cases and reject anything else.
|
| /OK3568_Linux_fs/buildroot/package/wpa_supplicant/ |
| H A D | 0002-ASN.1-Validate-DigestAlgorithmIdentifier-parameters.patch | 9 not check the parameters value at all which supported both these cases,
54 + * omit the parameters, but there are implementation that encode these
55 + * as a NULL element. Allow these two cases and reject anything else.
99 + * omit the parameters, but there are implementation that encode these
100 + * as a NULL element. Allow these two cases and reject anything else.
|
| /OK3568_Linux_fs/u-boot/lib/avb/libavb_ab/ |
| H A D | Kconfig | 7 This libavb_ab can suport these functions.
15 This libavb_ab can suport these functions.
23 This libavb_ab can suport these functions.
|
| /OK3568_Linux_fs/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
|
| /OK3568_Linux_fs/kernel/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
131 given even to these.) For example, loading a filesystem module via an
171 hole at the bottom of the stack to catch these overflows.
[all …]
|
| /OK3568_Linux_fs/kernel/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:
|
| /OK3568_Linux_fs/yocto/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 ${WORKDIR}/51-these-are-not-joysticks-rm.rules ${D}${nonarch_base_libdir}/udev/ru…
79 ${nonarch_base_libdir}/udev/rules.d/51-these-are-not-joysticks-rm.rules \
|
| /OK3568_Linux_fs/kernel/arch/mips/jazz/ |
| H A D | Kconfig | 9 kernel that runs on these, say Y here. For details about Linux on
21 kernel that runs on these, say Y here. For details about Linux on
32 kernel that runs on these, say Y here. For details about Linux on
|
| /OK3568_Linux_fs/kernel/Documentation/arm64/ |
| H A D | pointer-authentication.rst | 30 A subset of these instructions have been allocated from the HINT
32 these instructions behave as NOPs. Applications and libraries using
33 these instructions operate correctly regardless of the presence of the
94 requesting these two separate cpu features to be enabled. The current KVM
96 these userspace flags are checked before enabling pointer authentication.
98 if support is added in the future to allow these two features to be
105 Additionally, when these vcpu feature flags are not set then KVM will
|
| /OK3568_Linux_fs/kernel/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
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/media/drivers/ |
| H A D | bttv-devel.rst | 51 these pins. One register is the output enable register
54 you can get/set the status if these pins. They can be used for input
57 Most grabber board vendors use these pins to control an external chip
65 line for your board. The important fields are these two::
76 (``BT848_GPIO_OUT_EN``) will be set as these pins must be driven by the
87 card installed, you might to check out if you can read these registers
|