Home
last modified time | relevance | path

Searched +full:solid +full:- +full:state (Results 1 – 25 of 53) sorted by relevance

123

/freebsd/crypto/openssl/doc/man7/
H A Dlife_cycle-mac.pod5 life_cycle-mac - The MAC algorithm life-cycle
10 go through a number of stages in their life-cycle:
16 This state represents the MAC before it has been allocated. It is the
17 starting state for any life-cycle transitions.
21 This state represents the MAC after it has been allocated.
25 This state represents the MAC when it is set up and capable of processing
30 This state represents the MAC when it is set up and capable of processing
35 This state represents the MAC when it has generated output.
39 This state is entered when the MAC is freed. It is the terminal state
40 for all life-cycle transitions.
[all …]
H A Dlife_cycle-digest.pod5 life_cycle-digest - The digest algorithm life-cycle
9 All message digests (MDs) go through a number of stages in their life-cycle:
15 This state represents the MD before it has been allocated. It is the
16 starting state for any life-cycle transitions.
20 This state represents the MD after it has been allocated.
24 This state represents the MD when it is set up and capable of processing
29 This state represents the MD when it is set up and capable of processing
34 This state represents the MD when it has generated output.
38 This state is entered when the MD is freed. It is the terminal state
39 for all life-cycle transitions.
[all …]
H A Dlife_cycle-kdf.pod5 life_cycle-kdf - The KDF algorithm life-cycle
10 go through a number of stages in their life-cycle:
16 This state represents the KDF/PRF before it has been allocated. It is the
17 starting state for any life-cycle transitions.
21 This state represents the KDF/PRF after it has been allocated.
25 This state represents the KDF/PRF when it is set up and capable of generating
30 This state is entered when the KDF/PRF is freed. It is the terminal state
31 for all life-cycle transitions.
35 =head2 State Transition Diagram
37 The usual life-cycle of a KDF/PRF is illustrated:
[all …]
H A Dlife_cycle-rand.pod5 life_cycle-rand - The RAND algorithm life-cycle
10 go through a number of stages in their life-cycle:
16 This state represents the RAND before it has been allocated. It is the
17 starting state for any life-cycle transitions.
21 This state represents the RAND after it has been allocated but unable to
26 This state represents the RAND when it is set up and capable of generating
31 This state represents the RAND when it has been shutdown and it is no longer
36 This state is entered when the RAND is freed. It is the terminal state
37 for all life-cycle transitions.
41 =head2 State Transition Diagram
[all …]
H A Dlife_cycle-pkey.pod5 life_cycle-pkey - The PKEY algorithm life-cycle
9 All public keys (PKEYs) go through a number of stages in their life-cycle:
15 This state represents the PKEY before it has been allocated. It is the
16 starting state for any life-cycle transitions.
20 This state represents the PKEY after it has been allocated.
24 This state represents the PKEY when it is ready to perform a private key decapsulation
29 This state represents the PKEY when it is ready to decrypt some ciphertext.
33 This state represents the PKEY when it is ready to derive a shared secret.
37 This state represents the PKEY when it is ready to perform a private key signature
42 This state represents the PKEY when it is ready to perform a public key encapsulation
[all …]
H A Dlife_cycle-cipher.pod5 life_cycle-cipher - The cipher algorithm life-cycle
10 life-cycle:
16 This state represents the CIPHER before it has been allocated. It is the
17 starting state for any life-cycle transitions.
21 This state represents the CIPHER after it has been allocated.
47 This state represents the CIPHER when it has generated output.
51 This state is entered when the CIPHER is freed. It is the terminal state
52 for all life-cycle transitions.
56 =head2 State Transition Diagram
58 The usual life-cycle of a CIPHER is illustrated:
[all …]
/freebsd/contrib/libxo/xohtml/
H A Dxohtml.css8 #content-wrapper {
12 #target-history .empty {
14 text-align:center;
17 #command-history .empty {
19 padding-left: 20px;
23 font-size: 70%;
26 div[data-key] {
30 div.decoration, div.default, div.header-line {
32 font-family: monospace;
33 white-space: pre-wrap;
[all …]
/freebsd/contrib/libxo/xohtml/external/
H A Djquery.qtip.css2 * qTip2 - Pretty powerful tooltips - v2.1.1
15 left: -28000px;
16 top: -28000px;
19 max-width: 280px;
20 min-width: 50px;
22 font-size: 10.5px;
23 line-height: 12px;
27 box-shadow: none;
31 .qtip-content{
36 text-align: left;
[all …]
/freebsd/sys/contrib/openzfs/module/zfs/
H A Dvdev_draid_rand.c15 * This is xoroshiro128++ 1.0, one of our all-purpose, rock-solid,
16 * small-state generators. It is extremely (sub-ns) fast and it passes all
17 * tests we are aware of, but its state space is large enough only for
25 return (x << k) | (x >> (64 - k)); in rotl()
/freebsd/contrib/llvm-project/clang/lib/Rewrite/
H A DHTMLRewrite.cpp1 //== HTMLRewrite.cpp - Translate source code into prettified HTML --*- C++ -*-//
5 // SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
7 //===----------------------------------------------------------------------===//
12 //===----------------------------------------------------------------------===//
29 /// HighlightRange - Highlight a range in the source code with the specified
58 /// HighlightRange - This is the same as the above method, but takes
77 // to insert a close tag at the first non-whitespace before the newline. in HighlightRange()
82 // wait until we see a non-whitespace character. This prevents us from in HighlightRange()
84 // be put *after* whitespace on a non-blank line. in HighlightRange()
168 unsigned NumSpaces = 8-(ColNo&7); in EscapeText()
[all …]
/freebsd/contrib/libarchive/libarchive/
H A Darchive_read_support_format_rar5.c1 /*-
97 uint8_t solid : 1; /* Is this a solid stream? */ member
227 ssize_t window_mask; /* Convenience field; window_size - 1. */
236 in solid multiarchive archives. */
238 buffer, used in unpacking solid
269 /* Bit reader state. */
278 /* block_flags_u8 contain fields encoded in little-endian bitfield:
280 * - table present flag (shr 7, and 1),
281 * - last block flag (shr 6, and 1),
282 * - byte_count (shr 3, and 7),
[all …]
/freebsd/sys/contrib/device-tree/Bindings/media/i2c/
H A Dimx290.txt1 * Sony IMX290 1/2.8-Inch CMOS Image Sensor
3 The Sony IMX290 is a 1/2.8-Inch CMOS Solid-state image sensor with
4 Square Pixel for Color Cameras. It is programmable through I2C and 4-wire
6 Low voltage LVDS DDR output and CSI-2 serial data output. The CSI-2 bus is the
10 - compatible: Should be "sony,imx290"
11 - reg: I2C bus address of the device
12 - clocks: Reference to the xclk clock.
13 - clock-names: Should be "xclk".
14 - clock-frequency: Frequency of the xclk clock in Hz.
15 - vdddo-supply: Sensor digital IO regulator.
[all …]
H A Dsony,imx415.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Michae
[all...]
H A Dsony,imx296.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Sony IMX296 1/2.8-Inch CMOS Image Sensor
10 - Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
11 - Laurent Pinchart <laurent.pinchart@ideasonboard.com>
13 description: |-
14 The Sony IMX296 is a 1/2.9-Inch active pixel type CMOS Solid-state image
16 features a global shutter with variable charge-integration time. It is
17 programmable through I2C and 4-wire interfaces. The sensor output is
[all …]
H A Dsony,imx290.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Sony IMX290 1/2.8-Inch CMOS Image Sensor
10 - Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
11 - Laurent Pinchart <laurent.pinchart@ideasonboard.com>
13 description: |-
14 The Sony IMX290 is a 1/2.8-Inch CMOS Solid-state image sensor with Square
16 through I2C and 4-wire interfaces.
19 LVDS DDR output and CSI-2 serial data output. The CSI-2 bus is the default.
[all …]
/freebsd/share/man/man4/
H A Dmps.44 .\" Copyright (c) 2015-2017 Avago Technologies
5 .\" Copyright (c) 2015-2017 Broadcom Ltd.
45 .Nd "LSI Fusion-MPT 2 IT/IR 6Gb/s Serial Attached SCSI/SATA driver"
49 .Bd -ragged -offset indent
57 .Bd -literal -offset indent
64 Fusion-MPT 2 IT/IR
66 controllers and WarpDrive solid state storage cards.
72 .Bl -bullet -compact
86 Broadcom Ltd./Avago Tech (LSI) SSS6200 Solid State Storage
103 .Bd -literal -offset indent
[all …]
H A Dda.443 The direct access class includes disk, magneto-optical,
44 and solid-state devices.
61 The read cache is used to store data from device-initiated read ahead
79 a file system is non-deterministic and can cause corruption.
82 recently reported as complete, but it is none-the-less recommended that
100 concurrently, often re-ordering them to reduce the number and length of
110 the Read-Write Error Recovery mode page.
114 respectively, of the Read-Write Error Recovery page.
133 .Bl -tag -width 12
141 Disable detection of write-protected disks.
[all …]
H A Dmrsas.445 .Bd -ragged -offset indent
53 .Bd -literal -offset indent
71 A simple management interface is also provided on a per-controller basis via the
107 section to know more about driver priority for MR-Fusion devices.
110 will provide a priority of (-30) (between
119 Solid-state drives (SSD) get ATA TRIM support with
122 This may require configuring SSD as Non-RAID drive
130 .Bl -bullet -compact
154 .Bl -bullet -compact
174 .Bd -literal -offset indent
[all …]
/freebsd/lib/libvgl/
H A Dvgl.31 .\"-
210 The optional on-screen mouse pointer is shown if the
221 returns the current mouse pointer coordinates and button state in
267 draw a filled (solid) box with upper left hand corner at
285 draw a filled (solid) ellipse centered at
300 for the in-memory bitmap.
382 Passing an in-memory bitmap to this function results in error.
389 .Va object->VXsize
407 Passing an in-memory bitmap to this function results in error.
/freebsd/usr.sbin/crunch/
H A DREADME5 pub/bsd/crunch-0.2.tar.gz
14 * You can build crunched binaries even with no sources on-line, you
44 easily with a kernel for a decent one-disk fixit filesystem.
47 space-saving technique. Crunch automates the process by building the
68 bringing together a solid, state of the art development environment.
74 Crunch was written for the Maruti Hard Real-Time Operating System
76 and recovery procedures for our NetBSD-based development environment. It
77 is copyright (c) 1994 by the University of Maryland under a UCB-style
78 freely- redistributabl
[all...]
/freebsd/sys/contrib/device-tree/Bindings/mtd/
H A Dmtd-physmap.txt1 CFI or JEDEC memory-mapped NOR flash, MTD-RAM (NVRAM...)
3 Flash chips (Memory Technology Devices) are often used for solid state
6 - compatible : should contain the specific model of mtd chip(s)
7 used, if known, followed by either "cfi-flash", "jedec-flash",
8 "mtd-ram" or "mtd-rom".
9 - reg : Address range(s) of the mtd chip(s)
11 non-identical chips can be described in one node.
12 - bank-width : Width (in bytes) of the bank. Equal to the
14 - device-width : (optional) Width of a single mtd chip. If
15 omitted, assumed to be equal to 'bank-width'.
[all …]
H A Dmtd-physmap.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/mtd/mtd-physmap.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: CFI or JEDEC memory-mapped NOR flash, MTD-RAM (NVRAM...)
10 - Rob Herring <robh@kernel.org>
13 Flash chips (Memory Technology Devices) are often used for solid state
17 - $ref: mtd.yaml#
18 - $ref: /schemas/memory-controllers/mc-peripheral-props.yaml#
23 - items:
[all …]
/freebsd/sys/contrib/openzfs/include/sys/
H A Dvdev_impl.h9 * or https://opensource.org/licenses/CDDL-1.0.
152 uint32_t vq_nia_credit; /* Non-interactive I/Os credit. */
169 * On-disk indirect vdev state.
235 * requests may be inflated or incur device level read-modify-write
245 void *vdev_tsd; /* type-specific data */
246 vdev_t *vdev_top; /* top-level vdev */
254 boolean_t vdev_nonrot; /* true if solid state */
260 uint64_t vdev_crtxg; /* txg when top-level was added */
264 * Top-level vdev state.
272 txg_list_t vdev_ms_list; /* per-txg dirty metaslab lists */
[all …]
/freebsd/contrib/sendmail/src/
H A DTUNING1 # Copyright (c) 2001-2003, 2014 Proofpoint, Inc. and its suppliers.
8 # $Id: TUNING,v 1.22 2013-11-22 20:51:54 ca Exp $
34 * Mailing Lists and Large Aliases (1-n Mailing)
35 * 1-1 Mass Mailing
42 is non-trivial to combine low latency (fast delivery of incoming
50 -----------------------------------------------
58 disk is exceeded, which is true for almost every high-volume
70 -----------------------------------------------
92 Queueing up e-mail before delivery is done by a queue runner allows
96 on a queue group basis. Persistent queue runners (-qp) can be used
[all …]
/freebsd/sys/dev/isp/
H A DDriverManual.txt13 serve as a solid basis for attempting to understand where the driver
54 PCI and SBus SCSI cards, and now also drove the QLogic 2100 FC-AL HBA.
56 After this, ports to non-NetBSD platforms became interesting as well.
65 mode support has been added, and 2300 support as well as an FC-IP stack
71 Normally you design via top-down methodologies and set an initial goal
76 as I perceive them to be now- not necessarily what they started as.
90 as well as private loop and private loop, direct-attach topologies.
91 FC-IP support is also a goal.
119 The QLogic HBA cards all contain a tiny 16-bit RISC-like processor and
122 to a set of dual-ranked 16 bit incoming and outgoing mailbox registers
[all …]

123