/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
|
/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/linux/Documentation/ABI/testing/ |
H A D | sysfs-class-fpga-region | 5 Description: FPGA region id for compatibility check, e.g. compatibility
|
/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/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/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/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/qemu/docs/system/ |
H A D | cpu-models-mips.rst.inc | 13 compatibility is required, use the newest CPU model that is compatible 45 compatibility is required, use the newest CPU model that is compatible 89 compatibility is required, use the newest CPU model that is compatible
|
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/crypto/ |
H A D | inside-secure-safexcel.txt | 18 Backward compatibility: 19 Two compatibles are kept for backward compatibility, but shouldn't be used for
|
/openbmc/openbmc/poky/meta/recipes-sato/sato-icon-theme/ |
H A D | icon-naming-utils_0.8.90.bb | 2 SUMMARY = "Enables backwards compatibility with current desktop icon themes" 4 compatibility with current desktop icon themes, while migrating to the \
|
/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/openbmc/meta-openembedded/meta-networking/recipes-connectivity/openconnect/openconnect/ |
H A D | 0001-Shim-for-renaming-of-GNUTLS_NO_EXTENSIONS-in-GnuTLS-.patch | 8 then a backwards-compatibility shim was belatedly added in 32 + * backwards-compatibility shim was added in a subsequent commit, but
|
/openbmc/linux/Documentation/ABI/removed/ |
H A D | sysfs-selinux-checkreqprot | 13 This was a compatibility mechanism for legacy userspace and 24 The checkreqprot selinuxfs node will remain for backward compatibility
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-dbs/mysql/mariadb/ |
H A D | 0001-Ensure-compatibility-with-ARMv9-by-updating-.arch-di.patch | 4 Subject: [PATCH] Ensure compatibility with ARMv9 by updating .arch directive 9 to ensure compatibility with ARMv9 architectures.
|
/openbmc/linux/Documentation/admin-guide/ |
H A D | syscall-user-dispatch.rst | 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/u-boot/lib/lzma/ |
H A D | history.txt | 80 - Small changes for more compatibility with some C/C++ compilers. 95 - Small changes for more compatibility with some C/C++ compilers. 226 - More compatibility with some C++ compilers 262 keeping compatibility with original LZMA format
|
/openbmc/linux/Documentation/admin-guide/namespaces/ |
H A D | index.rst | 10 compatibility-list
|
/openbmc/linux/Documentation/devicetree/bindings/sound/ |
H A D | st,sti-asoc-card.txt | 35 "tx" for "st,sti-uni-player" compatibility 36 "rx" for "st,sti-uni-reader" compatibility 38 Required properties ("st,sti-uni-player" compatibility only):
|
/openbmc/qemu/docs/devel/migration/ |
H A D | index.rst | 12 compatibility
|
/openbmc/openbmc/poky/meta/recipes-devtools/python/ |
H A D | python-six.inc | 1 SUMMARY = "Python 2 and 3 compatibility library"
|
/openbmc/openbmc/poky/meta/classes-recipe/ |
H A D | populate_sdk.bbclass | 8 # This chunk simply facilitates compatibility with SDK only recipes.
|
/openbmc/linux/arch/m68k/fpsp040/ |
H A D | x_bsun.S | 6 | Copy the PC to FPIAR to maintain 881/882 compatibility
|
/openbmc/openbmc/poky/meta/recipes-devtools/pkgconf/ |
H A D | pkgconf_2.3.0.bb | 5 compatibility." 31 # pkg-config compatibility issues.
|
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/rdist/rdist-6.1.5/ |
H A D | rdist-6.1.5-oldpath.patch | 49 -/usr/ucb/oldrdist). In this way, you get compatibility with hosts 51 +Hat linux). In this way, you get compatibility with hosts
|