Searched full:compatibility (Results 1 – 25 of 282) sorted by relevance
12345678910>>...12
| /Documentation/devicetree/bindings/ptp/ |
| 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:
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-fpga-region | 5 Description: FPGA region id for compatibility check, e.g. compatibility
|
| /Documentation/admin-guide/ |
| 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
|
| D | abi-stable.rst | 7 restrictions, and backward compatibility for them will be guaranteed
|
| D | highuid.rst | 25 - Decide whether or not to keep backwards compatibility with the system
32 compatibility syscalls, if the OS being emulated used 16-bit UIDs, or
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-octeon.txt | 5 Compatibility with all cn3XXX, cn5XXX and cn6XXX SOCs.
11 Compatibility with cn78XX SOCs.
|
| /Documentation/devicetree/bindings/serial/ |
| 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
|
| /Documentation/devicetree/bindings/net/ |
| 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. */
|
| D | cavium-pip.txt | 12 Compatibility with all cn3XXX, cn5XXX and cn6XXX SOCs.
23 Compatibility with all cn3XXX, cn5XXX and cn6XXX SOCs.
34 Compatibility with all cn3XXX, cn5XXX and cn6XXX SOCs.
|
| D | cavium-mdio.txt | 6 "cavium,octeon-3860-mdio": Compatibility with all cn3XXX, cn5XXX
9 "cavium,thunder-8890-mdio": Compatibility with all cn8XXX SOCs.
|
| /Documentation/ABI/removed/ |
| D | sysfs-selinux-checkreqprot | 13 This was a compatibility mechanism for legacy userspace and
24 The checkreqprot selinuxfs node will remain for backward compatibility
|
| /Documentation/devicetree/bindings/crypto/ |
| D | inside-secure-safexcel.txt | 18 Backward compatibility:
19 Two compatibles are kept for backward compatibility, but shouldn't be used for
|
| D | qcom-qce.yaml | 21 description: Kept only for ABI backward compatibility
25 description: Kept only for ABI backward compatibility
|
| /Documentation/userspace-api/ |
| 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.
|
| /Documentation/admin-guide/namespaces/ |
| D | index.rst | 10 compatibility-list
|
| /Documentation/process/ |
| 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 …]
|
| /Documentation/livepatch/ |
| D | system-state.rst | 6 to provide more livepatches and maintain some compatibility between them.
24 - define compatibility between livepatches using a change id
65 2. Livepatch compatibility
|
| /Documentation/devicetree/bindings/mips/cavium/ |
| D | dma-engine.txt | 10 Compatibility with all cn52XX, cn56XX and cn6XXX SOCs.
|
| /Documentation/devicetree/bindings/powerpc/ |
| D | ibm,powerpc-cpu-features.txt | 13 enablement, privilege, and compatibility metadata.
40 This compatibility refers to backwards compatibility of the overall
51 compatibility, less the individual feature nodes. For example, an ISA v3.0
|
| /Documentation/devicetree/bindings/ata/ |
| D | marvell.txt | 4 - compatibility : "marvell,orion-sata" or "marvell,armada-370-sata"
|
| D | ahci-fsl-qoriq.txt | 5 - compatible: Compatibility string. Must be 'fsl,<chip>-ahci', where
|
| /Documentation/networking/ |
| D | openvswitch.rst | 29 Flow key compatibility
41 To support this forward and backward compatibility, whenever the
154 compatibility for applications that follow the rules listed under
155 "Flow key compatibility" above.
184 The application could, following the flow compatibility rules above,
189 across kernel versions even though it follows the compatibility rules.
|
| /Documentation/devicetree/bindings/usb/ |
| D | iproc-udc.txt | 9 - compatible: Add the compatibility strings for supported platforms.
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | opencores,or1k-pic.txt | 11 but this is only for backwards compatibility.
|
| /Documentation/devicetree/bindings/sound/ |
| 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):
|
12345678910>>...12