| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | Borceux | 5 compatibility/OldDiagram
6 compatibility/OldMaxiDiagram
7 compatibility/OldMicroDiagram
8 compatibility/OldMiniDiagram
9 compatibility/OldMultipleArrows
|
| H A D | UCL-1.0 | 1 Upstream Compatibility License v. 1.0 (UCL-1.0)
3 This Upstream Compatibility License (the "License") applies to any original work of authorship (the…
5 Licensed under the Upstream Compatibility License 1.0
13 …k You distribute or communicate shall be licensed under this Upstream Compatibility License and al…
14 …shall be licensed under both this Upstream Compatibility License and the Apache License 2.0 or lat…
48 …fied License is the "Open Software License" or "OSL" or the "Upstream Compatibility License" or "U…
|
| /openbmc/linux/Documentation/devicetree/bindings/ptp/ |
| H A D | brcm,ptp-dte.txt | 4 - compatible: should contain the core compatibility string
5 and the SoC compatibility string. The SoC
6 compatibility string is to handle SoC specific
8 Core compatibility string:
10 SoC compatibility strings:
|
| /openbmc/openbmc/poky/documentation/test-manual/ |
| H A D | yocto-project-compatible.rst | 46 The intent of the compatibility program is simple: if the layer passes the
47 compatibility tests, it is considered "well behaved" and should operate
50 The benefits of compatibility can be seen from multiple different user and
52 (a :ref:`overview-manual/concepts:bsp layer`), compatibility means the
55 a product, compatibility gives you a specification / standard you can
123 The project does test the compatibility status of the core project layers on
126 The official form to submit compatibility requests with is at
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | syscall-user-dispatch.rst | 10 Compatibility layers like Wine need a way to efficiently emulate system
22 invoking the kernel, when crossing the compatibility layer API
27 The goal of this design is to provide very quick compatibility layer
29 personality every time the compatibility layer executes. Instead, a
83 Syscall User Dispatch provides functionality for compatibility layers to
|
| /openbmc/linux/include/uapi/linux/ |
| H A D | route.h | 12 * for the purposes of compatibility only.
40 short rt_metric; /* +1 for binary compatibility! */
44 #define rt_mss rt_mtu /* Compatibility :-( */
58 #define RTF_MSS RTF_MTU /* Compatibility :-( */
|
| H A D | if.h | 23 #include <linux/libc-compat.h> /* for compatibility with glibc */
39 /* For glibc compatibility. An empty enum does not compile. */
83 /* for compatibility with glibc net/if.h */
110 /* for compatibility with glibc net/if.h */
194 /* for compatibility with glibc net/if.h */
232 /* for compatibility with glibc net/if.h */
284 /* for compatibility with glibc net/if.h */
|
| /openbmc/linux/drivers/message/fusion/lsi/ |
| H A D | mpi_log_sas.h | 270 /* Compatibility Error : IR Disabled */
272 /* Compatibility Error : Inquiry Command failed */
274 /* Compatibility Error : Device not direct access device */
276 /* Compatibility Error : Removable device found */
278 /* Compatibility Error : Device SCSI Version not 2 or higher */
280 /* Compatibility Error : SATA device, 48 BIT LBA not supported */
282 /* Compatibility Error : Device does not have 512 byte block sizes */
284 /* Compatibility Error : Volume Type check failed */
286 /* Compatibility Error : Volume Type is unsupported by FW */
288 /* Compatibility Error : Disk drive too small for use in volume */
[all …]
|
| /openbmc/qemu/docs/system/ |
| H A D | cpu-models-x86.rst.inc | 42 ABI compatibility levels for CPU models
45 The x86_64 architecture has a number of `ABI compatibility levels`_
49 table that follows illustrates which ABI compatibility levels
56 .. _ABI compatibility levels: https://gitlab.com/x86-psABIs/x86-64-ABI/
58 .. csv-table:: x86-64 ABI compatibility levels
71 compatibility is required, use the newest CPU model that is compatible
234 compatibility is required, use the newest CPU model that is compatible
292 for maximum guest compatibility.
307 none the less also be exposed for maximum guest compatibility as some
335 compatibility checks before launching guests, the default is guaranteed
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/net/ |
| H A D | marvell,pp2.yaml | 94 for backward compatibility but shouldn't be used for new
120 Legacy binding for backward compatibility.
216 port-id = <0>; /* For backward compatibility. */
224 port-id = <1>; /* For backward compatibility. */
261 port-id = <0>; /* For backward compatibility. */
280 port-id = <1>; /* For backward compatibility. */
302 port-id = <2>; /* For backward compatibility. */
|
| /openbmc/linux/fs/ext4/ |
| H A D | Kconfig | 2 # Ext3 configs are here for backward compatibility with old configs which may
9 This config option is here only for backward compatibility. ext3
18 This config option is here only for backward compatibility. ext3
26 This config option is here only for backward compatibility. ext3
|
| /openbmc/linux/drivers/net/ethernet/hisilicon/ |
| H A D | Kconfig | 104 tristate "Hisilicon HNS3 HCLGE Acceleration Engine & Compatibility Layer Support"
110 compatibility layer. The engine would be used in Hisilicon hip08 family of
123 tristate "Hisilicon HNS3VF Acceleration Engine & Compatibility Layer Support"
128 compatibility layer. The engine would be used in Hisilicon hip08 family of
|
| /openbmc/linux/tools/lib/bpf/ |
| H A D | bpf.h | 41 size_t sz; /* size of this struct for forward/backward compatibility */
65 size_t sz; /* size of this struct for forward/backward compatibility */
121 size_t sz; /* size of this struct for forward/backward compatibility */
156 size_t sz; /* size of this struct for forward/backward compatibility */
288 size_t sz; /* size of this struct for forward/backward compatibility */
302 size_t sz; /* size of this struct for forward/backward compatibility */
322 size_t sz; /* size of this struct for forward/backward compatibility */
336 size_t sz; /* size of this struct for forward/backward compatibility */
379 size_t sz; /* size of this struct for forward/backward compatibility */
430 size_t sz; /* size of this struct for forward/backward compatibility */
[all …]
|
| /openbmc/linux/tools/perf/Documentation/ |
| H A D | db-export.txt | 20 backward and forward compatibility, by following some simple rules:
30 backward compatibility by testing for the presence of new tables and columns
33 4. The export scripts themselves maintain forward compatibility (i.e. an existing
|
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 082.out | 54 compat=<str> - Compatibility level (v2 [0.10] or v3 [1.1])
80 compat=<str> - Compatibility level (v2 [0.10] or v3 [1.1])
106 compat=<str> - Compatibility level (v2 [0.10] or v3 [1.1])
132 compat=<str> - Compatibility level (v2 [0.10] or v3 [1.1])
158 compat=<str> - Compatibility level (v2 [0.10] or v3 [1.1])
184 compat=<str> - Compatibility level (v2 [0.10] or v3 [1.1])
210 compat=<str> - Compatibility level (v2 [0.10] or v3 [1.1])
236 compat=<str> - Compatibility level (v2 [0.10] or v3 [1.1])
277 compat=<str> - Compatibility level (v2 [0.10] or v3 [1.1])
364 compat=<str> - Compatibility level (v2 [0.10] or v3 [1.1])
[all …]
|
| /openbmc/linux/include/uapi/asm-generic/ |
| H A D | resource.h | 8 * ( Compatibility detail: there are architectures that have
10 * to keep that order for binary compatibility. The reasons
55 * Some architectures override this (for compatibility reasons):
|
| /openbmc/qemu/hw/ssi/ |
| H A D | stm32f2xx_spi.c | 90 "are included for compatibility\n", __func__); in stm32f2xx_spi_read()
94 "are included for compatibility\n", __func__); in stm32f2xx_spi_read()
98 "are included for compatibility\n", __func__); in stm32f2xx_spi_read()
102 "are included for compatibility\n", __func__); in stm32f2xx_spi_read()
106 "are included for compatibility\n", __func__); in stm32f2xx_spi_read()
|
| /openbmc/openbmc/poky/meta/recipes-devtools/patchelf/patchelf/ |
| H A D | 0002-align-startOffset-with-p_align-instead-of-pagesize-f.patch | 5 compatibility
15 p_align) for compatibility.
38 + compatibility. */
|
| /openbmc/qemu/hw/adc/ |
| H A D | stm32f2xx_adc.c | 129 "included for compatibility\n", __func__); in stm32f2xx_adc_read()
144 "included for compatibility\n", __func__); in stm32f2xx_adc_read()
152 "included for compatibility\n", __func__); in stm32f2xx_adc_read()
207 "included for compatibility\n", __func__); in stm32f2xx_adc_write()
228 "included for compatibility\n", __func__); in stm32f2xx_adc_write()
237 "included for compatibility\n", __func__); in stm32f2xx_adc_write()
|
| /openbmc/linux/Documentation/devicetree/bindings/serial/ |
| H A D | mvebu-uart.txt | 15 compatible string for backward compatibility), it will only work
20 should not be used and are supported only for backward compatibility.
31 - For backward compatibility reasons, a single element interrupts
|
| /openbmc/linux/Documentation/process/ |
| H A D | adding-syscalls.rst | 269 Compatibility System Calls (Generic)
276 However, there are a couple of situations where a compatibility layer is
290 The second situation that requires a compatibility layer is if one of the
294 32-bit values, which then need to be re-assembled in the compatibility layer.
297 does **not** need a compatibility layer; for example, :manpage:`splice(2)`'s arguments of
300 The compatibility version of the system call is called ``compat_sys_xyzzy()``,
356 Compatibility System Calls (x86)
359 To wire up the x86 architecture of a system call with a compatibility version,
375 the compatibility wrapper::
424 If the system call needs a compatibility layer (as in the previous section)
[all …]
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-fpga-region | 5 Description: FPGA region id for compatibility check, e.g. compatibility
|
| /openbmc/linux/Documentation/userspace-api/ |
| H A D | iommu.rst | 54 will break backward compatibility when offset moves. A new flag must
57 ensures backward compatibility.
69 Compatibility Checking
85 the compatibility upfront, as some subsequent errors happening during
91 headers. Backward compatibility is supported per feature flags.
|
| /openbmc/qemu/docs/devel/migration/ |
| H A D | main.rst | 233 state saved for a device can break migration compatibility unless
235 to maintain forward migration compatibility (i.e. migrating from
236 QEMU n->n+1) and there are users who benefit from backward compatibility
333 to send a subsection allows backward migration compatibility when
357 - removing them will break migration compatibility
360 compatibility.
363 compatibility.
367 a) Add a new property/compatibility/function in the same way for subsections above.
377 Note that for backward compatibility it's important to fill in the structure with
389 compatibility; in general most changes can be made by adding Subsections
[all …]
|
| /openbmc/qemu/include/qemu/ |
| H A D | hw-version.h | 15 * Do NOT change this string, or it will break compatibility on all
21 * QEMU_VERSION to guests in the past and need to keep compatibility.
|