| /src/tools/regression/sockets/unix_cmsg/ |
| H A D | unix_cmsg.t | 26 "1 Sending, receiving cmsgcred" \
27 "4 Sending cmsgcred, receiving sockcred" \
28 "5 Sending, receiving timeval" \
29 "6 Sending, receiving bintime" \
44 "2 Receiving sockcred (listening socket)" \
45 "3 Receiving sockcred (accepted socket)"
60 "1 Sending, receiving cmsgcred" \
61 "3 Sending cmsgcred, receiving sockcred" \
62 "4 Sending, receiving timeval" \
63 "5 Sending, receiving bintime" \
[all …]
|
| H A D | README | 57 1: Sending, receiving cmsgcred
63 2: Receiving sockcred (listening socket)
72 3: Receiving sockcred (accepted socket)
80 4: Sending cmsgcred, receiving sockcred
89 5: Sending, receiving timeval
95 6: Sending, receiving bintime
117 1: Sending, receiving cmsgcred
123 2: Receiving sockcred
130 3: Sending cmsgcred, receiving sockcred
139 4: Sending, receiving timeval
[all …]
|
| H A D | unix_cmsg.c | 84 .desc = "Sending, receiving cmsgcred"
88 .desc = "Receiving sockcred (listening socket)"
92 .desc = "Receiving sockcred (accepted socket)"
96 .desc = "Sending cmsgcred, receiving sockcred"
100 .desc = "Sending, receiving timeval"
104 .desc = "Sending, receiving bintime"
123 .desc = "Sending, receiving realtime"
129 .desc = "Sending, receiving monotonic time (uptime)"
144 .desc = "Sending, receiving cmsgcred"
148 .desc = "Receiving sockcred"
[all …]
|
| /src/crypto/openssl/doc/man3/ |
| H A D | SSL_get_stream_read_state.pod | 33 overall state of the receiving and sending parts of a QUIC stream, respectively.
59 signalled the end of the receiving part of the stream. Note that there may still
72 For SSL_get_stream_read_state(), this means that the receiving part of the
92 B<RESET_STREAM> frame for the receiving part of the stream; the receiving part
117 the receiving or sending parts of a stream, respectively. On success, the
|
| H A D | SSL_free.pod | 37 When used to free a QUIC stream SSL object, the respective sending and receiving
54 If the stream has a receiving part (in other words, if it is bidirectional or a
58 requests the reset of the receiving part of the stream using a QUIC STOP_SENDING
|
| /src/secure/lib/libcrypto/man/man3/ |
| H A D | SSL_get_stream_read_state.3 | 95 overall state of the receiving and sending parts of a QUIC stream, respectively.
115 signalled the end of the receiving part of the stream. Note that there may still
127 For \fBSSL_get_stream_read_state()\fR, this means that the receiving part of the
146 \&\fBRESET_STREAM\fR frame for the receiving part of the stream; the receiving part
168 the receiving or sending parts of a stream, respectively. On success, the
|
| H A D | SSL_free.3 | 98 When used to free a QUIC stream SSL object, the respective sending and receiving
109 If the stream has a receiving part (in other words, if it is bidirectional or a
113 requests the reset of the receiving part of the stream using a QUIC STOP_SENDING
|
| /src/sys/contrib/openzfs/man/man8/ |
| H A D | zfs-redact.8 | 113 The receiving system must have the
173 The receiving system must have the
180 features are active on the sending system, then the receiving system must have
210 features are active on the sending system, then the receiving system must have
246 the receiving system, which will disable the ability to do a raw send to that
253 that the holds be applied to the dataset on the receiving system.
295 The receiving system must also support this feature.
354 The receiving system must have the
375 features are active on the sending system, then the receiving system must have
402 the receiving syste
[all...] |
| H A D | zfs-send.8 | 113 The receiving system must have the
173 The receiving system must have the
180 features are active on the sending system, then the receiving system must have
210 features are active on the sending system, then the receiving system must have
246 the receiving system, which will disable the ability to do a raw send to that
253 that the holds be applied to the dataset on the receiving system.
295 The receiving system must also support this feature.
354 The receiving system must have the
375 features are active on the sending system, then the receiving system must have
402 the receiving system, which will disable the ability to do a raw send to that
[all …]
|
| /src/sys/contrib/device-tree/Bindings/media/ |
| H A D | qcom,sm8550-camss.yaml | 154 Input port for receiving CSI data on CSI0.
182 Input port for receiving CSI data on CSI1.
210 Input port for receiving CSI data on CSI2.
238 Input port for receiving CSI data on CSI3.
266 Input port for receiving CSI data on CSI4.
294 Input port for receiving CSI data on CSI5.
322 Input port for receiving CSI data on CSI6.
350 Input port for receiving CSI data on CSI7.
|
| H A D | qcom,sm8250-camss.yaml | 116 Input port for receiving CSI data.
144 Input port for receiving CSI data.
172 Input port for receiving CSI data.
200 Input port for receiving CSI data.
228 Input port for receiving CSI data.
256 Input port for receiving CSI data.
|
| H A D | qcom,sc7280-camss.yaml | 145 Input port for receiving CSI data on CSIPHY 0.
164 Input port for receiving CSI data on CSIPHY 1.
183 Input port for receiving CSI data on CSIPHY 2.
202 Input port for receiving CSI data on CSIPHY 3.
221 Input port for receiving CSI data on CSIPHY 4.
|
| H A D | qcom,msm8996-camss.yaml | 99 Input port for receiving CSI data.
130 Input port for receiving CSI data.
154 Input port for receiving CSI data.
178 Input port for receiving CSI data.
|
| H A D | qcom,sdm845-camss.yaml | 99 Input port for receiving CSI data.
123 Input port for receiving CSI data.
147 Input port for receiving CSI data.
171 Input port for receiving CSI data.
|
| H A D | qcom,sdm660-camss.yaml | 112 Input port for receiving CSI data.
136 Input port for receiving CSI data.
160 Input port for receiving CSI data.
184 Input port for receiving CSI data.
|
| /src/sys/contrib/openzfs/tests/zfs-tests/tests/functional/rsend/ |
| H A D | send-c_longname.ksh | 69 # Ensure the the receiving pool has feature@longname activated after receiving.
76 # Receiving of the stream on $POOL3 should fail as longname is not enabled
79 # Enable feature@longname and retry the receiving the stream.
|
| H A D | send_raw_large_blocks.ksh | 33 # Receiving a snapshot with large blocks and raw sending it succeeds.
45 log_assert "Receiving and raw sending a snapshot with large blocks succeeds"
79 log_pass "Receiving and raw sending a snapshot with large blocks succeeds"
|
| H A D | send_encrypted_incremental.ksh | 29 # Incrementally receiving a snapshot to an encrypted filesystem succeeds.
48 log_assert "Incrementally receiving a snapshot to an encrypted filesystem succeeds"
94 log_pass "Incrementally receiving a snapshot to an encrypted filesystem succeeds"
|
| /src/sys/contrib/device-tree/Bindings/serial/ |
| H A D | nvidia,tegra194-tcu.yaml | 17 for transmitting and one for receiving, that is used to communicate
39 List of phandles to mailbox channels used for receiving and
42 - description: mailbox for receiving data from hardware UART
|
| H A D | nvidia,tegra194-tcu.txt | 6 for transmitting and one for receiving, that is used to communicate
16 "rx" - Mailbox for receiving data from hardware UART
|
| /src/contrib/wpa/wpa_supplicant/ |
| H A D | ctrl_iface.h | 27 * Control interface backends call this function when receiving a message that
45 * Control interface backends call this function when receiving a message from
63 * Initialize the control interface and start receiving commands from external
103 * Initialize the global control interface and start receiving commands from
|
| /src/crypto/heimdal/appl/telnet/ |
| H A D | telnet.state | 3 (You need the localside, sending WILL/WONT & receiving DO/DONT, and
4 the remoteside, sending DO/DONT and receiving WILL/WONT)
35 When receiving NEW_STATE:
|
| /src/sys/contrib/device-tree/Bindings/sound/ |
| H A D | rockchip,rk3576-sai.yaml | 76 rockchip,sai-rx-route = <3> would mean sdi3 is receiving from data0, and
77 that there is only one receiving lane.
78 This property's absence is to be understood as only one receiving lane
|
| /src/tools/tools/netmap/ |
| H A D | lb.8 | 61 The receiving ends of the pipes
71 each group receiving all the packets in turn.
102 The group chaining assumes that the applications on the receiving end of the
|
| /src/sys/contrib/edk2/Include/Protocol/ |
| H A D | Tcp6.h | 287 /// EFI_CONNECTION_REFUSED: The receiving or transmission operation fails because this
342 /// it will pick up the first queued receiving token, update its
408 /// EFI_SUCCESS: The receiving or transmission operation
410 /// EFI_CONNECTION_FIN: The receiving operation fails because the communication peer
413 /// EFI_CONNECTION_RESET: The receiving or transmission operation fails
416 /// EFI_ABORTED: The receiving or transmission is aborted.
430 /// EFI_SECURITY_VIOLATION: The receiving or transmission
437 /// When this token is used for receiving, RxData is a pointer to
511 transmission and receiving buffer directly without informing the communication peer.
682 Places an asynchronous receive request into the receiving queue.
[all …]
|