| /freebsd/lib/libc/posix1e/ |
| H A D | acl.3 | 63 This function is described in
67 This function is described in
71 This function is described in
78 This function is described in
82 This function is described in
86 This function is described in
93 These functions are described in
103 These functions are described in
110 This functions are described in
114 This function is described in
[all …]
|
| H A D | mac.3 | 73 must first be prepared using the interfaces described in
88 This function, described in
93 These functions, described in
98 These functions, described in
102 These functions, described in
106 This function, described in
110 This function, described in
114 This function, described in
119 These functions, described in
127 This function is described in
[all …]
|
| H A D | posix1e.3 | 46 implements POSIX.1e interface for access control lists, described in
54 implements a POSIX.1e-like mandatory access control interface, described in
72 functionality described in POSIX.1.
75 in extended attributes, described in
106 POSIX.1e is described in IEEE POSIX.1e draft 17.
|
| /freebsd/share/man/man9/ |
| H A D | intro.9 | 86 Formatted output and logging functions are described by
97 variables and functions is described by
123 Atomic primitives are described by
185 The implementation of access control lists for filesystems is described by
191 .\" The buffer cache is described by:
214 A framework for managing packet output queues is described by
224 described by
229 The low-level packet filter interface is described by
236 The subsystem for IEEE 802.11 wireless networking is described by
239 A framework for modular TCP implementations is described by
[all …]
|
| H A D | sglist.9 | 233 family of routines can be used to append the physical address ranges described
241 function appends the physical address ranges described by a single kernel
252 function appends the physical address ranges described by a single bio
259 function appends the physical address ranges described by the
281 function appends the physical address ranges described by an entire mbuf
289 function appends the physical address ranges described by a single mbuf
306 function appends physical address ranges described by the scatter/gather list
320 function appends the physical address ranges described by a
332 function appends the physical address ranges described by a single user
363 it appends the physical address ranges described by
[all …]
|
| H A D | shm_map.9 | 66 It maps the region of that object described by
144 The requested region described by
166 The address range described by
172 The address range described by
|
| /freebsd/crypto/openssl/doc/man7/ |
| H A D | provider.pod | 58 libraries, and the available functions are further described in
63 The functions that may be offered are further described in
117 The functions the provider can offer are described in
125 The functions the provider can offer are described in
133 The functions the provider can offer are described in
141 The functions the provider can offer are described in
149 The functions the provider can offer are described in
157 The functions the provider can offer are described in
164 The functions the provider can offer are described in L<provider-kem(7)>.
171 The functions the provider can offer are described in
[all …]
|
| H A D | EVP_SIGNATURE-DSA.pod | 11 L<EVP_PKEY_sign(3)> is DER encoded ASN.1 in the form described in
27 The settable parameters are described in L<provider-signature(7)>.
40 The gettable parameters are described in L<provider-signature(7)>.
|
| /freebsd/secure/lib/libcrypto/man/man7/ |
| H A D | provider.7 | 190 libraries, and the available functions are further described in
195 The functions that may be offered are further described in
247 The functions the provider can offer are described in
254 The functions the provider can offer are described in
261 The functions the provider can offer are described in
268 The functions the provider can offer are described in
275 The functions the provider can offer are described in
282 The functions the provider can offer are described in
288 The functions the provider can offer are described in \fBprovider\-kem\fR\|(7).
294 The functions the provider can offer are described in
[all …]
|
| /freebsd/contrib/ntp/html/ |
| H A D | warp.html | 35 …ion Service (IERS). Reckoning with leap seconds in the NTP timescale is described in the white pap…
36 …described in the white paper <a href="http://www.eecis.udel.edu/~mills/leap.html">The NTP Timesc…
47 …anged between the client and server using the <em>on-wire protocol</em> described in the white pa…
48 …described on the <a href="poll.html">Poll Process</a> page to maximize accuracy while minimizing n…
54 …ing delays. A more accurate measurement uses <em>drivestamps</em>, as described on the <a href="…
55 …described on the <a href="filter.html">Clock Filter Algorithm</a> page selects the offset and…
56 …described on the <a href="prefer.html">Mitigation Rules and the <tt>prefer</tt> Keyword</a> page c…
|
| /freebsd/sys/contrib/device-tree/Bindings/regulator/ |
| H A D | qcom,smd-rpm-regulator.txt | 44 described in the data sheet
57 described in the data sheet
77 described in the data sheet
95 described in the data sheet
145 described in the data sheet
154 described in the data sheet
186 described in the data sheet
215 described in the data sheet
221 described in the data sheet
239 described in the data sheet
|
| H A D | qcom,spmi-regulator.txt | 45 described in the data sheet.
60 described in the data sheet.
78 described in the data sheet.
98 described in the data sheet
129 described in the data sheet.
138 described in the data sheet.
153 described in the data sheet.
167 described in the data sheet.
184 described in the data sheet.
223 see regulator.txt - with additional custom properties described below:
|
| /freebsd/sys/contrib/device-tree/Bindings/i3c/ |
| H A D | i3c.yaml | 14 I3C busses can be described with a node for the primary I3C controller device
25 Each I2C device connected to the bus should be described in a subnode.
29 described in the device tree. This being said, one might want to attach
31 described in the device tree, which in turn means we have to describe
53 I2C devices described in the device tree to determine the maximum I2C
74 All properties described in dtschema schemas/i2c/i2c-controller.yaml
190 * resources described in the DT.
|
| H A D | i3c.txt | 29 values of I2C devices described in the device tree to determine
35 Each I2C device connected to the bus should be described in a subnode. All
36 properties described in Documentation/devicetree/bindings/i2c/i2c.txt are
72 are thus discoverable. So, by default, I3C devices do not have to be described
75 and those resources may have to be described in the device tree, which in turn
134 * resources described in the DT.
|
| /freebsd/lib/libpmc/ |
| H A D | pmc_name_of_capability.3 | 69 PMC capabilities are described in
77 PMC classes are described in
85 CPU types known to the library are described in
93 PMC row dispositions are described in
111 PMC modes are described in
|
| /freebsd/crypto/openssl/doc/man3/ |
| H A D | BIO_connect.pod | 27 B<BIO_SOCK_REUSEADDR>, which is described in L</FLAGS> below.
32 The flags are described in L</FLAGS> below.
38 The flags are described in L</FLAGS> below.
44 on the accepted socket. The flags are described in L</FLAGS> below.
106 Use the functions described above instead.
|
| /freebsd/crypto/openssh/ |
| H A D | ssh_config.5 | 196 accept the tokens described in the
212 lists and may use the wildcard and negation operators described in the
271 using the format described in the
446 the tokens described in the
448 section and environment variables as described in the
671 Specify the path to the control socket used for connection sharing as described
680 the tokens described in the
682 section and environment variables as described in the
884 using the format described in the
1056 accept the tokens described in the
[all …]
|
| /freebsd/lib/libsys/ |
| H A D | rctl_add_rule.2 | 81 Rule format is as described in
103 Filter syntax is as described in
121 Filter syntax is as described in
135 Filter syntax is as described in
145 This section explains how the rule and filter format described in
|
| /freebsd/stand/man/ |
| H A D | loader_4th.8 | 143 The commands are described in the
148 The environment variables common to all interpreters are described in the
182 receiving special treatment in Step 2, described below.
203 An exception to this parsing rule exists, and is described in
207 If interpreted, they behave exactly as described previously.
276 the latter were already described.
282 The words falling in the two other groups are described in the
461 configuration files, as described in
|
| /freebsd/sys/contrib/device-tree/Bindings/display/armada/ |
| H A D | marvell,dove-lcd.txt | 7 - port: video output port with endpoints, as described by graph.txt
11 - clocks: as described by clock-bindings.txt
12 - clock-names: as described by clock-bindings.txt
|
| /freebsd/lib/libc/gen/ |
| H A D | posix_spawn.3 | 360 to fail, an error value is returned as described by
374 described by
390 to fail, an error value is returned as described by
403 to fail, an error value is returned as described by
419 to fail, an error value is returned as described by
425 may, by itself, result in any of the errors described by
427 in addition to those described by
|
| /freebsd/sys/contrib/device-tree/Bindings/mmc/ |
| H A D | hi3798cv200-dw-mshc.txt | 8 differences between the core Synopsys dw mshc controller properties described
17 "ciu" - The ciu clock described in synopsys-dw-mshc.txt.
18 "biu" - The biu clock described in synopsys-dw-mshc.txt.
|
| /freebsd/lib/libutil/ |
| H A D | login_times.3 | 95 described period begins and ends.
123 function determines whether the given time described by the struct tm
124 passed as the second parameter falls within the period described
165 function returns non-zero if the given time falls within the period described
|
| /freebsd/share/doc/psd/05.sysman/ |
| H A D | 1.5.t | 62 The generic operations applying to many of these types are described
63 in section 2.1. Naming contexts, files and directories are described in
65 Terminals and (structured and unstructured) devices are described
190 \(dg The facilities described in this section are not included
204 and are described in the programmers manual.
|
| /freebsd/sys/contrib/device-tree/Bindings/media/ |
| H A D | video-mux.txt | 5 on the active input port is passed through to the output port. Muxes described
6 by this binding are controlled by a multiplexer controller that is described by
19 ports node as described in Documentation/devicetree/bindings/graph.txt.
|