Searched refs:implemented (Results 1 – 25 of 625) sorted by relevance
12345678910>>...25
28 These instructions are fully implemented.40 These instructions are fully implemented. They store/load three words58 FLT/FIX are fully implemented.60 RFS/WFS are fully implemented.73 These are fully implemented.87 These are fully implemented.103 This is fully implemented.110 These are fully implemented.116 These are fully implemented.121 These are implemented. URD is implemented using the same code as the RND[all …]
57 Value of 0xFF indicates that this option is not implemented66 Value of 0xFF indicates that this option is not implemented76 Value of 0xFF indicates that this option is not implemented84 Value of 0xFF indicates that this option is not implemented95 Value of 0xFF indicates that this option is not implemented105 Value of 0xFF indicates that this option is not implemented115 Value of 0xFF indicates that this option is not implemented126 Value of 0xFF indicates that this option is not implemented137 Value of 0xFF indicates that this option is not implemented149 Value of 0xFF indicates that this option is not implemented
7 This document describes the devlink features implemented by the ``mlx5``13 .. list-table:: Generic parameters implemented23 .. list-table:: Driver-specific parameters implemented54 .. list-table:: devlink info versions implemented
7 This document describes the devlink features implemented by the ``bnxt``13 .. list-table:: Generic parameters implemented31 .. list-table:: Driver-specific parameters implemented50 .. list-table:: devlink info versions implemented
7 This document describes the devlink features implemented by the ``mlxsw``13 .. list-table:: Generic parameters implemented23 .. list-table:: Driver-specific parameters implemented45 .. list-table:: devlink info versions implemented
7 This document describes the devlink features implemented by the ``octeontx2 AF, PF and VF``15 .. list-table:: Driver-specific parameters implemented31 .. list-table:: Driver-specific parameters implemented
7 This document describes the devlink features implemented by the ``nfp``13 .. list-table:: Generic parameters implemented27 .. list-table:: devlink info versions implemented
7 This document describes the devlink features implemented by the ``mlx4``13 .. list-table:: Generic parameters implemented27 .. list-table:: Driver-specific parameters implemented
7 This document describes the devlink features implemented by the ``am65-cpsw-nuss``16 .. list-table:: Driver-specific parameters implemented
7 This document describes the devlink features implemented by the ``hns3``17 .. list-table:: devlink info versions implemented
7 This document describes the devlink features implemented by the ``qed`` core15 .. list-table:: Driver-specific parameters implemented
7 This document describes the devlink features implemented by the ``ionic``15 .. list-table:: devlink info versions implemented
7 This document describes the devlink features implemented by the ``ti-cpsw-switch``16 .. list-table:: Driver-specific parameters implemented
7 This document describes the devlink features implemented by the ``mv88e6xxx``15 .. list-table:: Driver-specific parameters implemented
13 .. list-table:: Generic parameters implemented23 .. list-table:: Driver-specific parameters implemented34 can be implemented.
13 Enable this to support USB PHY implemented on USB2 controller25 Enable this to support USB PHY implemented in USB3 controller35 Enable this to support PHY implemented in PCIe controller45 Enable this to support PHY implemented in AHCI controller
8 implemented using ARM specific CPU features or instructions.17 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented27 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented37 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented46 SHA-256 secure hash standard (DFIPS 180-2) implemented54 SHA-256 secure hash standard (DFIPS 180-2) implemented62 SHA-512 secure hash standard (DFIPS 180-2) implemented
33 * CAIF Link Layer, implemented as NET devices.68 each layer described in the specification is implemented as a separate layer.79 specification is implemented in a separate c-file.179 The IP interface and CAIF socket API are implemented on top of the189 The Link Layer is implemented as Linux network devices (struct net_device).194 Therefore a flow-control mechanism is implemented where the physical
82 * system acoustics optimizations (not implemented)93 * 1 Imon input (not implemented)94 * PECI support (not implemented)95 * 2 GPIO pins (not implemented)96 * system acoustics optimizations (not implemented)
38 This is implemented using READ_ONCE()/WRITE_ONCE() and47 CPU (A-cumulative property). This is implemented using smp_mb().54 (A-cumulative property). This is implemented using61 after the acquire operation executes. This is implemented using68 Control dependency on stores are not implemented using any explicit
656 cap->implemented = 0; in ceph_add_cap()748 cap->implemented |= issued; in ceph_add_cap()793 if (implemented) in __ceph_caps_issued()794 *implemented = 0; in __ceph_caps_issued()802 if (implemented) in __ceph_caps_issued()803 *implemented |= cap->implemented; in __ceph_caps_issued()1406 arg->caps = cap->implemented; in __prep_cap()2649 int have, implemented; in try_get_cap_refs() local3496 cap->implemented |= newcaps; in handle_cap_grant()3789 int implemented = 0; in handle_cap_trunc() local[all …]
35 Supported. Both PEC and block process call support is implemented. Slave36 mode or host notification are not yet implemented.
11 This driver is a shim for firmware implemented in ARM's TrustZone19 implemented in firmware. The driver itself doesn't contain much logic and is
4 systems within the Tegra SoC. It is implemented through a mailbox-21 the mailbox subsystem, and the specifiers implemented by the relevant
15 architecture can be implemented with this style, the definitions51 implemented by most applications. Hence this area is revisited.111 Not all ioctl's are implemented in the driver from the API, the other112 features of the hardware that cannot be implemented by the API are achieved
Completed in 46 milliseconds