| /freebsd/tests/sys/netpfil/pf/ |
| H A D | sctp.py | 277 # Sanity check, we can communicate with the primary address.
318 # Sanity check, we can communicate with the primary address.
329 # We can still communicate
356 # We can still communicate
391 # Sanity check, we can communicate with the primary address.
425 # Sanity check, we can communicate with the primary address.
485 # Sanity check, we can communicate with the primary address.
526 # Sanity check, we can communicate with the primary address.
585 # Sanity check, we can communicate with the primary address.
626 # Sanity check, we can communicate with the primary address.
[all …]
|
| /freebsd/share/man/man4/ |
| H A D | bridge.4 | 164 To allow the host to communicate with bridge members, IP addresses
277 communicate with each other.
278 For example, two interfaces in VLAN 10 would be able to communicate
332 Sometimes it is useful to allow the host itself to communicate in a VLAN,
339 For example, to allow the host to communicate in VLAN 10:
348 To restrict which interfaces may communicate in which VLANs,
376 For example, to allow an interface to communicate in VLANs 10, 20,
639 interfaces can only communicate in their assigned VLANs,
642 is a trunk port which can communicate in either VLAN:
659 communicate in VLANs 10 and 20:
|
| /freebsd/include/rpcsvc/ |
| H A D | ypclnt.h | 45 #define YPERR_PMAP 9 /* can't communicate with portmapper */
46 #define YPERR_YPBIND 10 /* can't communicate with ypbind */
47 #define YPERR_YPSERV 11 /* can't communicate with ypserv */
|
| /freebsd/crypto/heimdal/kuser/ |
| H A D | kdigest-commands.in | 40 help = "Kerberos realm to communicate with"
85 help = "Kerberos realm to communicate with"
269 help = "Kerberos realm to communicate with"
|
| H A D | kdigest.8 | 73 Kerberos realm to communicate with
111 Kerberos realm to communicate with
246 Kerberos realm to communicate with
|
| /freebsd/sys/contrib/device-tree/Bindings/firmware/xilinx/ |
| H A D | xlnx,zynqmp-firmware.txt | 6 ZynqMP has an interface to communicate with secure firmware. Firmware
8 used by any driver to communicate to PMUFW(Platform Management Unit).
|
| H A D | xlnx,zynqmp-firmware.yaml | 13 firmware. ZynqMP has an interface to communicate with secure firmware.
15 can be used by any driver to communicate to PMUFW(Platform Management Unit).
|
| /freebsd/contrib/llvm-project/llvm/include/llvm/CodeGen/ |
| H A D | SwitchLoweringUtils.h | 106 /// This structure is used to communicate between SelectionDAGBuilder and
264 /// Vector of CaseBlock structures used to communicate SwitchInst code
268 /// Vector of JumpTable structures used to communicate SwitchInst code
272 /// Vector of BitTestBlock structures used to communicate SwitchInst code
|
| /freebsd/share/doc/smm/12.timed/ |
| H A D | timed.ms | 185 The master sends this message to a slave to communicate
343 if it is a slave, it will communicate the desired date to the master.
352 A slave that has received a Set Date message will communicate the
410 communicate this location to \fItimedc\fP.
|
| /freebsd/contrib/openpam/doc/man/ |
| H A D | pam.man | 25 callback which it can use to communicate with the user.
26 Some modules may use specialized conversation functions to communicate
|
| H A D | pam.3 | 86 callback which it can use to communicate with the user.
87 Some modules may use specialized conversation functions to communicate
|
| /freebsd/share/doc/psd/21.ipc/ |
| H A D | 3.t | 57 communicate. A service is assigned a name which is intended
70 host wishes to communicate. This ability to have hosts named in
134 expected that almost all software that has to communicate
220 a process wishes to communicate with a machine, it should ask the
|
| /freebsd/crypto/krb5/src/include/ |
| H A D | k5-spake.h | 60 /* SPAKEChallenge is sent from the KDC to the client to communicate its group
68 /* SPAKEResponse is sent from the client to the KDC to communicate its public
|
| /freebsd/tools/test/hwpmc/ |
| H A D | pmctest.py | 80 counters = p.communicate()[0]
91 result = p.communicate()[0]
|
| /freebsd/tests/sys/file/ |
| H A D | flock_helper.c | 183 * test. We use a pipe to communicate with the child. in test2()
254 * test. We use a pipe to communicate with the child. in test3()
324 * test. We use a pipe to communicate with the child. in test4()
598 * test. We use a pipe to communicate with the child. in test7()
670 * test. We use a pipe to communicate with the child. in test8()
747 * test. We use a pipe to communicate with the child. in test9()
819 * test. We use a pipe to communicate with the child. in test10()
972 * test. We use a pipe to communicate with the child. in test12()
1049 * test. We use a pipe to communicate with the child. in test13()
1333 * test. We use a pipe to communicate with the child. in test15()
[all …]
|
| /freebsd/contrib/wpa/src/drivers/ |
| H A D | driver_macsec_linux.c | 717 DRV_PREFIX "failed to communicate: %d (%s)", in do_dump()
787 DRV_PREFIX "failed to communicate: %d (%s)", in macsec_drv_set_receive_lowest_pn()
849 DRV_PREFIX "failed to communicate: %d (%s)", in macsec_drv_set_transmit_next_pn()
897 DRV_PREFIX "%s: failed to communicate: %d (%s)", in macsec_drv_create_receive_sc()
933 DRV_PREFIX "%s: failed to communicate: %d (%s)", in macsec_drv_delete_receive_sc()
992 DRV_PREFIX "%s: failed to communicate: %d (%s)", in macsec_drv_create_receive_sa()
1038 DRV_PREFIX "%s: failed to communicate: %d (%s)", in macsec_drv_delete_receive_sa()
1074 DRV_PREFIX "%s: failed to communicate: %d (%s)", in set_active_rx_sa()
1315 DRV_PREFIX "%s: failed to communicate: %d (%s)", in macsec_drv_create_transmit_sa()
1358 DRV_PREFIX "%s: failed to communicate: %d (%s)", in macsec_drv_delete_transmit_sa()
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/soc/qcom/ |
| H A D | rpmh-rsc.txt | 86 Drivers that want to use the RSC to communicate with RPMH must specify their
87 bindings as child nodes of the RSC controllers they wish to communicate with.
|
| /freebsd/sys/contrib/device-tree/Bindings/mailbox/ |
| H A D | fsl,mu.yaml | 14 communicate and coordinate by passing messages (e.g. data, status
50 - description: To communicate with i.MX8 SCU with fast IPC
|
| H A D | rockchip-mailbox.txt | 3 The Rockchip mailbox is used by the Rockchip CPU cores to communicate
|
| /freebsd/contrib/sendmail/libmilter/docs/ |
| H A D | design.html | 98 communicate with the MTA. These parameters, as well as the
120 Each filter may communicate with multiple MTAs at the same time over
|
| /freebsd/sys/contrib/device-tree/Bindings/arm/msm/ |
| H A D | ssbi.txt | 4 communicate with a limited range of devices (mostly power management
|
| /freebsd/sys/contrib/device-tree/Bindings/i2c/ |
| H A D | i2c-pca-platform.txt | 5 and allows the parallel bus system to communicate bi-directionally
|
| /freebsd/sys/contrib/device-tree/Bindings/crypto/ |
| H A D | brcm,spu-crypto.txt | 14 - mboxes: The mailbox channel to be used to communicate with the SPU.
|
| /freebsd/lib/libthr/tests/ |
| H A D | atfork_test.c | 107 * use its exit status to communicate to us if the callback was not executed
227 * of tests as the parent and continues to communicate the results of those
|
| /freebsd/sys/contrib/device-tree/Bindings/iio/humidity/ |
| H A D | dht11.yaml | 27 Single, interrupt capable, GPIO used to communicate with the device.
|