| /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:
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-fpga-region | 5 Description: FPGA region id for compatibility check, e.g. compatibility
|
| /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
|
| /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
|
| /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
88 Syscall User Dispatch provides functionality for compatibility layers to
|
| H A D | devices.rst | 94 /dev/core /proc/kcore symbolic Backward compatibility
95 /dev/ramdisk ram0 symbolic Backward compatibility
96 /dev/ftape qft0 symbolic Backward compatibility
97 /dev/bttv0 video0 symbolic Backward compatibility
98 /dev/radio radio0 symbolic Backward compatibility
99 /dev/i2o* /dev/i2o/* symbolic Backward compatibility
|
| /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):
|
| /linux/Documentation/admin-guide/namespaces/ |
| H A D | index.rst | 10 compatibility-list
|
| /linux/arch/m68k/fpsp040/ |
| H A D | x_bsun.S | 6 | Copy the PC to FPIAR to maintain 881/882 compatibility
|
| /linux/arch/arm/boot/dts/st/ |
| H A D | stm32mp157a-avenger96.dts | 10 /* This DT is here only for backward compatibility */
|
| /linux/Documentation/devicetree/bindings/powerpc/ |
| H 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/arm64/boot/dts/marvell/ |
| H A D | armada-ap807.dtsi | 27 "marvell,armada-ap806-sdhci"; /* Backward compatibility */
|
| /linux/Documentation/livepatch/ |
| H 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/drivers/hwtracing/stm/ |
| H A D | Kconfig | 21 driver for compatibility with your existing STM setup.
27 backwards compatibility for your existing setup, say Y.
|
| /linux/Documentation/networking/ |
| H A D | gen_stats.rst | 59 TCA_STATS/TCA_XSTATS backward compatibility:
63 compatibility by calling the compat wrappers to keep providing the
|
| H 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.
|
| H A D | alias.rst | 10 for backwards compatibility.
|
| /linux/Documentation/process/ |
| H A D | adding-syscalls.rst | 322 However, there are a couple of situations where a compatibility layer is
336 The second situation that requires a compatibility layer is if one of the
340 32-bit values, which then need to be re-assembled in the compatibility layer.
343 does **not** need a compatibility layer; for example, :manpage:`splice(2)`'s arguments of
346 The compatibility version of the system call is called ``compat_sys_xyzzy()``,
429 On arm64, there is a dedicated syscall table for compatibility system calls
440 To wire up the x86 architecture of a system call with a compatibility version,
456 the compatibility wrapper::
505 If the system call needs a compatibility layer (as in the previous section)
583 new syscall, or needs to be shared between a syscall and its compatibility
[all …]
|
| /linux/Documentation/userspace-api/media/dvb/ |
| H A D | frontend_legacy_api.rst | 24 kernel due to compatibility issues only. Their usage is strongly not
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H 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)
209 ``videodev.h`` for compatibility with the original ``videodev.h`` file.
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:
275 change may *break compatibility* with applications depending on the
[all …]
|
| /linux/Documentation/devicetree/bindings/net/ |
| H A D | hisilicon-hns-mdio.txt | 8 while "hisilicon,mdio" is optional for backwards compatibility only on
|
| /linux/Documentation/devicetree/bindings/usb/ |
| H A D | iproc-udc.txt | 9 - compatible: Add the compatibility strings for supported platforms.
|
| /linux/Documentation/bpf/ |
| H A D | bpf_design_QA.rst | 125 A: This is artifact of compatibility with classic BPF. Modern
307 Q: What is the compatibility story for special BPF types in map values?
313 kernel preserve backwards compatibility for these features?
319 the kernel will preserve backwards compatibility, as they are part of UAPI.
337 In other words, no backwards compatibility is guaranteed if one using a type
340 Q: What is the compatibility story for special BPF types in allocated objects?
344 compatibility for these features?
|
| /linux/Documentation/filesystems/ext4/ |
| H A D | eainode.rst | 14 backward compatibility with older versions of this feature, the
|
| /linux/drivers/media/platform/synopsys/hdmirx/ |
| H A D | Kconfig | 25 to 4k@30Hz, which have best compatibility with HDMI transmitters.
|