/linux/Documentation/devicetree/bindings/ptp/ |
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:
|
/linux/Documentation/ABI/testing/ |
A D | sysfs-class-fpga-region | 5 Description: FPGA region id for compatibility check, e.g. compatibility
|
/linux/tools/perf/Documentation/ |
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
|
/linux/fs/ext4/ |
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
|
/linux/Documentation/admin-guide/ |
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 79 Syscall User Dispatch provides functionality for compatibility layers to
|
A D | devices.rst | 95 /dev/core /proc/kcore symbolic Backward compatibility 96 /dev/ramdisk ram0 symbolic Backward compatibility 97 /dev/ftape qft0 symbolic Backward compatibility 98 /dev/bttv0 video0 symbolic Backward compatibility 99 /dev/radio radio0 symbolic Backward compatibility 100 /dev/i2o* /dev/i2o/* symbolic Backward compatibility
|
A D | abi-stable.rst | 7 restrictions, and backward compatibility for them will be guaranteed
|
A 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
|
/linux/Documentation/devicetree/bindings/crypto/ |
A D | inside-secure-safexcel.txt | 18 Backward compatibility: 19 Two compatibles are kept for backward compatibility, but shouldn't be used for
|
/linux/Documentation/ABI/obsolete/ |
A D | sysfs-selinux-checkreqprot | 10 This was a compatibility mechanism for legacy userspace and 21 The checkreqprot selinuxfs node will remain for backward compatibility
|
/linux/Documentation/devicetree/bindings/mtd/ |
A D | partition.txt | 30 For backwards compatibility partitions as direct subnodes of the flash device are 32 NOTE: also for backwards compatibility, direct subnodes that have a compatible
|
/linux/Documentation/devicetree/bindings/sound/ |
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):
|
/linux/Documentation/devicetree/bindings/net/ |
A D | mscc-ocelot.txt | 15 - "ptp" (optional due to backward compatibility) 23 "ptp_rdy" which is optional due to backward compatibility.
|
/linux/Documentation/devicetree/bindings/serial/ |
A D | mvebu-uart.txt | 15 compatible string for backward compatibility), it will only work 28 - For backward compatibility reasons, a single element interrupts
|
/linux/Documentation/admin-guide/namespaces/ |
A D | index.rst | 10 compatibility-list
|
/linux/Documentation/devicetree/bindings/powerpc/ |
A 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
|
/linux/arch/m68k/fpsp040/ |
A D | x_bsun.S | 6 | Copy the PC to FPIAR to maintain 881/882 compatibility
|
/linux/arch/arm/boot/dts/ |
A D | stm32mp157a-avenger96.dts | 10 /* This DT is here only for backward compatibility */
|
/linux/Documentation/userspace-api/ |
A D | iommu.rst | 54 will break backward compatibility when offset moves. A new flag must 57 ensures backward compatibility. 85 the compatibility upfront, as some subsequent errors happening during 91 headers. Backward compatibility is supported per feature flags.
|
/linux/Documentation/livepatch/ |
A 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
|
/linux/Documentation/process/ |
A D | adding-syscalls.rst | 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. 300 The compatibility version of the system call is called ``compat_sys_xyzzy()``, 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) 502 new syscall, or needs to be shared between a syscall and its compatibility 505 syscall stub (``sys_xyzzy()``), the compatibility syscall stub 522 architecture-specific compatibility wrappers, or other code in arch/. [all …]
|
/linux/Documentation/userspace-api/media/v4l/ |
A D | hist-v4l2.rst | 78 Added a v4l to V4L2 ioctl compatibility layer to videodev.c. Driver 89 1999-03-31: Better compatibility for v4l memory capture ioctls. Requires 90 changes to drivers to fully support new compatibility features, see 116 was changed for compatibility with v4l. (1999-08-30) 221 2001-01-25: A possible driver-level compatibility problem between the 233 correctly through the backward compatibility layer. [Solution?] 244 compatibility* as the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and 270 removed. This change *breaks compatibility* with earlier versions: 840 changes may *break the compatibility* with older drivers and 877 extending the structure. This may **break compatibility** with [all …]
|
/linux/drivers/hwtracing/stm/ |
A D | Kconfig | 22 driver for compatibility with your existing STM setup. 28 backwards compatibility for your existing setup, say Y.
|
/linux/Documentation/networking/ |
A D | gen_stats.rst | 59 TCA_STATS/TCA_XSTATS backward compatibility: 63 compatibility by calling the compat wrappers to keep providing the
|
A 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.
|