Home
last modified time | relevance | path

Searched full:specifications (Results 1 – 25 of 485) sorted by relevance

12345678910>>...20

/freebsd/sys/contrib/device-tree/Bindings/soundwire/
H A Dqcom,sdw.txt71 More info in MIPI Alliance SoundWire 1.0 Specifications.
80 More info in MIPI Alliance SoundWire 1.0 Specifications.
90 More info in MIPI Alliance SoundWire 1.0 Specifications.
98 More info in MIPI Alliance SoundWire 1.0 Specifications.
109 More info in MIPI Alliance SoundWire 1.0 Specifications.
119 More info in MIPI Alliance SoundWire 1.0 Specifications.
129 More info in MIPI Alliance SoundWire 1.0 Specifications.
140 More info in MIPI Alliance SoundWire 1.0 Specifications.
151 More info in MIPI Alliance SoundWire 1.0 Specifications.
163 More info in MIPI Alliance SoundWire 1.0 Specifications.
[all …]
H A Dqcom,soundwire.yaml82 More info in MIPI Alliance SoundWire 1.0 Specifications.
93 More info in MIPI Alliance SoundWire 1.0 Specifications.
104 More info in MIPI Alliance SoundWire 1.0 Specifications.
115 More info in MIPI Alliance SoundWire 1.0 Specifications.
126 More info in MIPI Alliance SoundWire 1.0 Specifications.
137 More info in MIPI Alliance SoundWire 1.0 Specifications.
150 More info in MIPI Alliance SoundWire 1.0 Specifications.
167 More info in MIPI Alliance SoundWire 1.0 Specifications.
184 More info in MIPI Alliance SoundWire 1.0 Specifications.
200 More info in MIPI Alliance SoundWire 1.0 Specifications
[all...]
/freebsd/share/doc/psd/15.yacc/
H A Dss0157 specifications.
163 provided as part of the input specifications,
168 specifications.
169 For example, the specifications may be self contradictory, or they may
177 While Yacc cannot handle all possible specifications, its power
183 Yacc specifications for their input revealed errors of
225 style and efficiency of the specifications.
H A Dss937 9: Hints for Preparing Specifications
40 and clear specifications.
85 writing specifications of sequences and lists:
/freebsd/share/doc/smm/02.config/
H A Da.t55 /* configuration specifications */
66 /* system configuration specifications */
88 /* option specifications */
100 /* device specifications */
149 interconnection specifications.
H A D4.t46 device specifications.
148 are one or more specifications indicating where the root file system
169 allows specifications to be continued across multiple lines
237 Device specifications
318 specifications would be used:
H A D6.t70 which may be configured with pseudo-device specifications.
98 This last file may override specifications in the first two.
121 Optional file specifications include a list of one or more system
H A D5.t97 To this we must then add the specifications for three
141 we currently have. The revised device specifications would then be:
241 is needed. The additional device specifications are show below.
/freebsd/share/man/man4/
H A Daibs.457 the supposed range specifications of each sensor's input
61 The range specifications are as follows:
66 Temperature sensors have two upper specifications.
74 Sensor readings and the range specifications are made available through the
151 Sensor range specifications are supported by
/freebsd/sys/contrib/device-tree/Bindings/display/panel/
H A Dlvds.yaml17 following specifications.
26 Device compatible with those specifications have been marketed under the
52 [VESA] specifications. Data are transferred as follows on 3 LVDS lanes.
63 specifications. Data are transferred as follows on 4 LVDS lanes.
/freebsd/contrib/ofed/libibverbs/man/
H A Dibv_create_flow.343 IBV_FLOW_ATTR_NORMAL = 0x0, /* Steering according to rule specifications */
70 IBV_FLOW_SPEC_INNER = 0x100, /* Flag making L2/L3/L4 specifications to be appl…
98 …iority domain will always supersede a lower priority domain when their flow specifications overlap.
143 5. No specifications are needed for IBV_FLOW_ATTR_SNIFFER rule type.
/freebsd/lib/libc/stdtime/
H A Dstrptime.366 string consists of zero or more conversion specifications and
71 All conversion specifications are identical to those described in
89 string does not contain enough conversion specifications to completely
/freebsd/crypto/openssl/include/internal/
H A Ddso.h71 * callbacks) that merge two file specifications. They are passed a DSO
73 * object) and two file specifications to merge. They should either return
77 * taken from each of the file specifications and added together in whatever
111 * specifications, or if the callback isn't set it will instead use the
/freebsd/usr.sbin/syslogd/
H A Dsyslog.conf.548 specifications (separations appear alone on their lines),
165 specifications given.
235 As for program specifications, multiple comma-separated
236 values may be specified for hostname specifications.
454 specifications performs exact match filtering against explicit field only.
/freebsd/usr.bin/sort/
H A Dsort.1.in143 specifications, they apply globally to all sort keys.
239 option, it applies globally to all key specifications.
244 argument of the key specifications.
337 Try to use radix sort, if the sort specifications allow.
346 Try to use quick sort, if the sort specifications allow.
352 Try to use heap sort, if the sort specifications allow.
/freebsd/contrib/llvm-project/clang/lib/Sema/
H A DSemaExceptionSpec.cpp1 //===--- SemaExceptionSpec.cpp - C++ Exception Specifications ---*- C++ -*-===//
43 /// specifications. Libstdc++ 6.1 (released 2016-04-27) appears to have
169 // WebAssembly reference types can't be used in exception specifications. in CheckSpecifiedExceptionType()
187 // C++17 removes this rule in favor of putting exception specifications into in CheckDistantExceptionSpec()
351 // specifications. in CheckEquivalentExceptionSpec()
396 // Allow missing exception specifications in redeclarations as an extension, in CheckEquivalentExceptionSpec()
498 // In Microsoft mode, mismatching exception specifications just cause a warning. in CheckEquivalentExceptionSpec()
505 /// exception specifications. See C++ [except.spec]p3.
507 /// \return \c false if the exception specifications match, \c true if there is
530 // C++0x [except.spec]p3: Two exception-specifications are compatible if: in CheckEquivalentExceptionSpecImpl()
[all …]
/freebsd/usr.sbin/crunch/crunchgen/
H A Dcrunchgen.156 utility reads in the specifications in
170 utility reads specifications from the
206 A list of library specifications to be included in the crunched binary link.
211 A list of library specifications to be dynamically linked in the
/freebsd/lib/libsys/
H A Dmq_close.231 .\" Specifications Issue 6, Copyright (C) 2001-2004 by the Institute of
98 Specifications Issue 6, Copyright (C) 2001-2004 by the Institute of
H A Dmq_setattr.231 .\" Specifications Issue 6, Copyright (C) 2001-2004 by the Institute of
116 Specifications Issue 6, Copyright (C) 2001-2004 by the Institute of
H A Dmq_unlink.230 .\" Specifications Issue 6, Copyright (C) 2001-2004 by the Institute of
113 Specifications Issue 6, Copyright (C) 2001-2004 by the Institute of
H A Dmq_getattr.231 .\" Specifications Issue 6, Copyright (C) 2001-2004 by the Institute of
120 Specifications Issue 6, Copyright (C) 2001-2004 by the Institute of
/freebsd/lib/libc/gen/
H A Dtcgetwinsize.328 .\" Specifications Issue 8, Copyright (C) 2020 by the Institute of
155 Base Specifications, Issue 8.
/freebsd/usr.sbin/setfmac/
H A Dsetfsmac.861 Apply the specifications in
79 Apply the specifications in
/freebsd/contrib/mtree/
H A Dmtree.8175 If this option is specified twice, the two specifications are compared
177 The specifications will be sorted like output generated using
379 Specifications are mostly composed of
698 should be run against the on-line specifications and the final checksum
700 While it is possible for the bad guys to change the on-line specifications
/freebsd/sys/contrib/openzfs/tests/zfs-tests/tests/functional/cli_root/zpool_split/
H A Dzpool_split_devices.ksh68 # "good" device specifications
76 # "bad" device specifications

12345678910>>...20