Home
last modified time | relevance | path

Searched full:compatibility (Results 1 – 25 of 757) sorted by relevance

12345678910>>...31

/openbmc/openbmc/poky/meta/files/common-licenses/
H A DBorceux5 compatibility/OldDiagram
6 compatibility/OldMaxiDiagram
7 compatibility/OldMicroDiagram
8 compatibility/OldMiniDiagram
9 compatibility/OldMultipleArrows
H A DUCL-1.01 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/openbmc/poky/documentation/test-manual/
H A Dyocto-project-compatible.rst46 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/openbmc/poky/meta/recipes-devtools/patchelf/patchelf/
H A D0002-align-startOffset-with-p_align-instead-of-pagesize-f.patch5 compatibility
15 p_align) for compatibility.
38 + compatibility. */
/openbmc/qemu/include/qemu/
H A Dhw-version.h15 * 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.
/openbmc/qemu/docs/sphinx/
H A Dcompat.py2 Sphinx cross-version compatibility goop
74 # xref compatibility hacks for Sphinx < 4.1 #
78 # subsequent 3 compatibility classes can be removed. Anywhere in
95 Compatibility workaround for Sphinx versions prior to 4.1.0.
123 # XRefRole features not supported by this compatibility shim;
188 # When we require Sphinx > 6.2.0, the rest of this compatibility hack
/openbmc/qemu/docs/system/
H A Dcpu-models-x86.rst.inc42 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
276 compatibility is required, use the newest CPU model that is compatible
334 for maximum guest compatibility.
349 none the less also be exposed for maximum guest compatibility as some
377 compatibility checks before launching guests, the default is guaranteed
[all …]
H A Dcpu-models-mips.rst.inc13 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
/openbmc/qemu/hw/ssi/
H A Dstm32f2xx_spi.c90 "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-sato/sato-icon-theme/
H A Dicon-naming-utils_0.8.90.bb2 SUMMARY = "Enables backwards compatibility with current desktop icon themes"
4 compatibility with current desktop icon themes, while migrating to the \
/openbmc/qemu/hw/adc/
H A Dstm32f2xx_adc.c129 "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/qemu/tests/qemu-iotests/
H A D082.out54 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/entity-manager/schemas/
H A Dibm.json38 "title": "System compatibility",
39compatibility strings for systems, where a 'system' is roughly defined as the combination of a cha…
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/openconnect/openconnect/
H A D0001-Shim-for-renaming-of-GNUTLS_NO_EXTENSIONS-in-GnuTLS-.patch8 then a backwards-compatibility shim was belatedly added in
32 + * backwards-compatibility shim was added in a subsequent commit, but
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-dbs/mysql/mariadb/
H A D0001-Ensure-compatibility-with-ARMv9-by-updating-.arch-di.patch4 Subject: [PATCH] Ensure compatibility with ARMv9 by updating .arch directive
9 to ensure compatibility with ARMv9 architectures.
/openbmc/qemu/docs/devel/migration/
H A Dmain.rst235 state saved for a device can break migration compatibility unless
237 to maintain forward migration compatibility (i.e. migrating from
238 QEMU n->n+1) and there are users who benefit from backward compatibility
335 to send a subsection allows backward migration compatibility when
359 - removing them will break migration compatibility
362 compatibility.
365 compatibility.
369 a) Add a new property/compatibility/function in the same way for subsections above.
379 Note that for backward compatibility it's important to fill in the structure with
391 compatibility; in general most changes can be made by adding Subsections
[all …]
H A Dindex.rst12 compatibility
/openbmc/qemu/target/ppc/
H A Dcompat.c90 * on POWER9 for POWER8 compatibility guests, and it's very
182 error_setg(errp, "Unknown compatibility PVR 0x%08"PRIx32, compat_pvr); in ppc_set_compat()
185 error_setg(errp, "Compatibility PVR 0x%08"PRIx32" not valid for CPU", in ppc_set_compat()
198 "Unable to set CPU compatibility mode in KVM"); in ppc_set_compat()
319 error_setg(errp, "Invalid compatibility mode \"%s\"", value); in ppc_compat_prop_set()
/openbmc/openbmc/meta-openembedded/meta-filesystems/dynamic-layers/meta-python/recipes-support/gpiod-sysfs-proxy/gpiod-sysfs-proxy/
H A Dgpiod-sysfs-proxy.init.in8 # Short-Description: User-space, libgpiod-based compatibility layer for linux GPIO sysfs interfa…
22 DESC="/sys/class/gpio compatibility layer"
/openbmc/phosphor-state-manager/
H A Dhost_state_manager_main.cpp58 // now.For backward compatibility if there is a legacy persist file in main()
77 // For backwards compatibility, request a busname without host id if in main()
/openbmc/u-boot/arch/x86/cpu/i386/
H A Dcall64.S57 * in 32bit compatibility mode with EFER.LME = 1, CS.L = 0, CS.D = 1
73 /* Jump from 32bit compatibility mode into 64bit mode. */
/openbmc/u-boot/arch/powerpc/include/asm/
H A Dmpc85xx_gpio.h70 /* Compatibility shim */ in gpio_request()
76 /* Compatibility shim */ in gpio_free()
/openbmc/openbmc/poky/meta/classes-recipe/
H A Dpopulate_sdk.bbclass8 # This chunk simply facilitates compatibility with SDK only recipes.
/openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/
H A Dpython3-txaio_23.1.1.bb1 DESCRIPTION = "Compatibility API between asyncio/Twisted/Trollius"
/openbmc/qemu/docs/system/arm/
H A Dsbsa.rst76 fw compatibility are introduced. The ``machine-version-minor`` value
77 is updated when features are added that don't break fw compatibility.

12345678910>>...31