| /illumos-gate/usr/src/man/man3xcurses/ |
| H A D | curses.3xcurses | 8 curses \- introduction and overview of X/Open Curses
17 X/Open Curses is a terminal-independent package, providing a common user
21 low-level details about individual terminals.
118 An integral type that holds an OR-ed set of attributes. The attributes
138 non-spacing wide characters, and zero or more attributes of any type. See
149 An integral type whose values are formed by OR-ing an \fB"unsigned char"\fR
212 Window objects are two-dimensional arrays of characters and their renditions.
214 the terminal screen. You can use the \fBnewwin\fR(3XCURSES) function to create
225 There are three sub-types of windows:
264 A terminal is the input and output device which character-based applications
[all …]
|
| /freebsd/sys/contrib/device-tree/src/arm/marvell/ |
| H A D | armada-385-turris-omnia.dts | 1 // SPDX-License-Identifier: (GPL-2.0 OR MIT)
5 * Copyright (C) 2016 Uwe Kleine-König <uwe@kleine-koenig.org>
8 * Schematic available at https://www.turris.cz/doc/_media/rtrom01-schema.pdf
11 /dts-v1/;
13 #include <dt-bindings/gpio/gpio.h>
14 #include <dt-bindings/input/input.h>
15 #include <dt-bindings/leds/common.h>
16 #include "armada-385.dtsi"
20 compatible = "cznic,turris-omnia", "marvell,armada385", "marvell,armada380";
23 stdout-path = &uart0;
[all …]
|
| /freebsd/share/man/man9/ |
| H A D | buf_ring.9 | 40 .Nd multi-producer, {single, multi}-consumer lock-less ring buffer
65 functions provide a lock-less multi-producer and lock-less multi-consumer as
66 well as single-consumer ring buffer.
70 function is used to allocate a buf_ring ring buffer with
81 function is used to free a buf_ring.
86 function is used to enqueue a buffer to a buf_ring.
90 function is a multi-consumer safe way of dequeueing elements from a buf_ring.
94 function is a single-consumer interface to dequeue elements - requiring
99 function returns the number of elements in a buf_ring.
103 function returns
[all …]
|
| /illumos-gate/usr/src/man/man3c/ |
| H A D | getnetgrent.3c | 8 getnetgrent, getnetgrent_r, setnetgrent, endnetgrent, innetgr \- get network
49 The function \fBinnetgr()\fR returns \fB1\fR if there is a netgroup
57 The \fBinnetgr()\fR function is safe for use in single-threaded and
65 The function \fBsetnetgrent()\fR establishes the network group specified in the
70 Successive calls to the function \fBgetnetgrent()\fR will enumerate the members
99 This implementation is not safe for use in multi-threaded applications.
102 The function \fBgetnetgrent_r()\fR is similar to \fBgetnetgrent()\fR function,
107 associated with the triple. The \fBgetnetgrent_r()\fR function is safe for use
108 both in single-threaded and multi-threaded applications.
111 The function \fBendnetgrent()\fR frees the space allocated by the previous
[all …]
|
| H A D | c16rtomb.3c | 22 .Nd convert wide-characters to character sequences
60 functions convert wide-character sequences into a series of multi-byte
63 .Bl -tag -width wcrtomb_l
65 A UTF-16 code sequence, where every code point is represented by one or
68 The UTF-16 encoding will encode certain Unicode code points as a pair of
69 two 16-bit code sequences, commonly referred to as a surrogate pair.
71 A UTF-32 code sequence, where every code point is represented by a
76 Wide characters, being a 32-bit value where every code point is
86 The functions all work by looking at the passed in wide-character
113 .Sy UTF-8
[all …]
|
| H A D | mbrtoc16.3c | 65 functions convert character sequences, which may contain multi-byte
68 .Bl -tag -width mbrtowc_l
70 A UTF-16 code sequence, where every code point is represented by one or
73 The UTF-16 encoding will encode certain Unicode code points as a pair of
74 two 16-bit code sequences, commonly referred to as a surrogate pair.
76 A UTF-32 code sequence, where every code point is represented by a
80 Wide characters, being a 32-bit value where every code point is
103 .Sy UTF-8
105 .Sy en_US.UTF-8 ,
106 UTF-8 multi-byte character sequences that represent Unicode code points
[all …]
|
| /freebsd/secure/lib/libcrypto/man/man7/ |
| H A D | ossl-guide-quic-multi-stream.7 | 1 .\" -*- mode: troff; coding: utf-8 -*-
57 .IX Title "OSSL-GUIDE-QUIC-MULTI-STREAM 7ossl"
58 .TH OSSL-GUIDE-QUIC-MULTI-STREAM 7ossl 2025-09-30 3.5.4 OpenSSL
64 ossl\-guide\-quic\-multi\-stream
65 \&\- OpenSSL Guide: Writing a simple multi\-stream QUIC client
69 QUIC multi-stream application. It assumes a basic understanding of QUIC and how
70 it is used in OpenSSL. See \fBossl\-guide\-quic\-introduction\fR\|(7) and
71 \&\fBossl\-guide\-quic\-client\-block\fR\|(7).
74 In a QUIC multi-stream application we separate out the concepts of a QUIC
98 (see \fBossl\-guide\-libraries\-introduction\fR\|(7)). In particular most OpenSSL
[all …]
|
| H A D | openssl-quic.7 | 1 .\" -*- mode: troff; coding: utf-8 -*-
57 .IX Title "OPENSSL-QUIC 7ossl"
58 .TH OPENSSL-QUIC 7ossl 2025-09-30 3.5.4 OpenSSL
64 openssl\-quic \- OpenSSL QUIC
82 Default stream mode versus multi-stream mode for clients;
84 The changes to existing libssl APIs which are driven by QUIC-related
92 New, QUIC-specific APIs.
96 stream mode, which is intended to provide compatibility with existing non-QUIC
100 client-initiated or server-initiated from a QUIC perspective depends on whether
105 instead adopt the multi-stream API. See the RECOMMENDATIONS FOR NEW APPLICATIONS
[all …]
|
| /freebsd/sys/contrib/xz-embedded/linux/include/linux/ |
| H A D | xz.h | 5 * Igor Pavlov <https://7-zip.org/>
37 * enum xz_mode - Operation mode
39 * @XZ_SINGLE: Single-call mode. This uses less RAM than
40 * multi-call modes, because the LZMA2
45 * @XZ_PREALLOC: Multi-call mode with preallocated LZMA2
49 * @XZ_DYNALLOC: Multi-call mode. The LZMA2 dictionary is
68 * enum xz_ret - Return codes
71 * return code is possible only in multi-call mode
75 * is still possible in multi-call mode by simply
90 * only in multi-call mode (XZ_PREALLOC or
[all …]
|
| /illumos-gate/usr/src/test/util-tests/tests/cpmvln/ |
| H A D | overwrite.ksh | 20 # program may be set up to operate interactively (-i), to not touch a file if it
21 # already exists (-n), and to forcefully remove it anyways (-f). cp implements
22 # -i and -n, -f means something different. mv implements all three flags. ln
23 # implements -i and -f (-n is a pseudo-default).
26 unalias -a
27 set -o pipefail
28 export LANG=C.UTF-8
33 MV=${MV:-"/usr/bin/mv"}
34 XMV=${XMV:-"/usr/xpg4/bin/mv"}
35 CP=${CP:-"/usr/bin/cp"}
[all …]
|
| /freebsd/crypto/openssl/doc/man7/ |
| H A D | ossl-guide-quic-multi-stream.pod | 6 demos/guide/quic-multi-stream.c
12 ossl-guide-quic-multi-stream
13 - OpenSSL Guide: Writing a simple multi-stream QUIC client
18 QUIC multi-stream application. It assumes a basic understanding of QUIC and how
19 it is used in OpenSSL. See L<ossl-guide-quic-introduction(7)> and
20 L<ossl-guide-quic-client-block(7)>.
24 In a QUIC multi-stream application we separate out the concepts of a QUIC
48 (see L<ossl-guide-libraries-introduction(7)>). In particular most OpenSSL
64 (by default) the default stream will be a client-initiated bi-directional
67 stream (whether it is bi-directional or uni-directional).
[all …]
|
| /illumos-gate/usr/src/man/man9f/ |
| H A D | csx_Parse_CISTPL_LONGLINK_MFC.9f | 8 csx_Parse_CISTPL_LONGLINK_MFC \- parse the Multi-Function tuple
47 \fBCISTPL_LONGLINK_MFC\fR tuple information upon return from this function.
51 This function parses the Multi-Function tuple, \fBCISTPL_LONGLINK_MFC,\fR into
56 function-specific \fBCIS \fRfor each function on a multi-function card.
64 uint32_t function[CIS_MAX_FUNCTIONS].tas
65 uint32_t function[CIS_MAX_FUNCTIONS].addr
95 \fB\fBfunction[CIS_MAX_FUNCTIONS].tas\fR \fR
99 This field provides the target address space for each function on the \fBPC
124 \fB\fBfunction[CIS_MAX_FUNCTIONS].addr\fR \fR
128 This field provides the target address offset for each function on the \fBPC
[all …]
|
| /freebsd/sys/contrib/device-tree/src/powerpc/ |
| H A D | turris1x.dts | 1 // SPDX-License-Identifier: GPL-2.0+
5 * Copyright 2013 - 2022 CZ.NIC z.s.p.o. (http://www.nic.cz/)
8 * and available at: https://docs.turris.cz/hw/turris-1x/turris-1x/
11 #include <dt-bindings/gpio/gpio.h>
12 #include <dt-bindings/interrupt-controller/irq.h>
13 #include <dt-bindings/leds/common.h>
14 /include/ "fsl/p2020si-pre.dtsi"
41 gpio-controller@18 {
45 #gpio-cells = <2>;
46 gpio-controller;
[all …]
|
| /freebsd/secure/lib/libcrypto/man/man3/ |
| H A D | RSA_get0_key.3 | 1 .\" -*- mode: troff; coding: utf-8 -*-
58 .TH RSA_GET0_KEY 3ossl 2025-09-30 3.5.4 OpenSSL
72 \&\- Routines for getting and setting data in an RSA object
118 return a \fBBIGNUM\fR. Refer to \fBEVP_PKEY\-DH\fR\|(7) for more information.
129 For multi-prime RSA (defined in RFC 8017), there are also one or more
143 parameters to the function. The values \fBn\fR and \fBe\fR must be non-NULL
144 the first time this function is called on a given RSA object. The
147 Calling this function transfers the memory management of the values to
149 should not be freed by the caller after this function has been called.
158 ignore NULL parameters but return values for other, non-NULL, parameters.
[all …]
|
| /freebsd/contrib/bearssl/inc/ |
| H A D | bearssl_hash.h | 45 * For each implemented hash function, of name "`xxx`", the following
48 * - `br_xxx_vtable`
52 * - `br_xxx_SIZE`
55 * hash function.
57 * - `br_xxx_ID`
60 * function. Such identifiers are used with HMAC and signature
64 * standard](https://tools.ietf.org/html/rfc5246#section-7.4.1.4.1),
66 * 1 to 6 for MD5, SHA-1, SHA-224, SHA-256, SHA-384 and SHA-512,
69 * - `br_xxx_context`
75 * capture the function state at some point. Computations that use
[all …]
|
| /illumos-gate/usr/src/man/man3socket/ |
| H A D | getnetbyname.3socket | 8 getnetent_r, setnetent, endnetent \- get network entry
11 \fBcc\fR [ \fIflag\fR ... ] \fIfile\fR ... \fB-lsocket\fR \fB -lnsl \fR [ \fIlibrary\fR ... ]
77 \fBinet_network()\fR function returns a value in host byte order that is
95 pre-CIDR (Classless Inter-Domain Routing) subnet mask. For example:
115 J., and Varadhan, K. \fIRFC 1519, Classless Inter-Domain Routing (CIDR): an
125 of network entries. This function should be called before the first call to
128 is non-zero, the system may keep allocated resources such as open file
144 for use in multi-threaded applications.
151 Each reentrant interface performs the same operation as its non-reentrant
154 results, and are safe for use in both single-threaded and multi-threaded
[all …]
|
| /freebsd/crypto/openssl/doc/man3/ |
| H A D | RSA_get0_key.pod | 13 - Routines for getting and setting data in an RSA object
57 return a B<BIGNUM>. Refer to L<EVP_PKEY-DH(7)> for more information.
68 For multi-prime RSA (defined in RFC 8017), there are also one or more
82 parameters to the function. The values B<n> and B<e> must be non-NULL
83 the first time this function is called on a given RSA object. The
86 Calling this function transfers the memory management of the values to
88 should not be freed by the caller after this function has been called.
97 ignore NULL parameters but return values for other, non-NULL, parameters.
99 For multi-prime RSA, RSA_get0_multi_prime_factors() and RSA_get0_multi_prime_params()
102 sets a collect of multi-prime 'triplet' members (prime, exponent and coefficient)
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/leds/ |
| H A D | cznic,turris-omnia-leds.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/leds/cznic,turris-omnia-leds.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Marek Behún <kabel@kernel.org>
20 const: cznic,turris-omnia-leds
26 "#address-cells":
29 "#size-cells":
33 "^multi-led@[0-9a-b]$":
35 $ref: leds-class-multicolor.yaml#
[all …]
|
| /illumos-gate/usr/src/uts/common/io/qede/579xx/hsi/hw/ |
| H A D | reg_addr_bb.h | 9 * or http://opensource.org/licenses/CDDL-1.0.
23 * Copyright 2014-2017 Cavium, Inc.
30 * at http://opensource.org/licenses/CDDL-1.0
39 … 0x001d00UL //Access:R DataWidth:0x1 // Multi Field Register.
44 … 0x001d04UL //Access:RW DataWidth:0x1 // Multi Field Register.
49 … 0x001d08UL //Access:WR DataWidth:0x1 // Multi Field Register.
54 … 0x001d0cUL //Access:RC DataWidth:0x1 // Multi Field Register.
84 …- For ending "endless completion". 0 - When receiving a completion timeout while receiving a compl…
85 … DataWidth:0x4 // 0 - TXCPL sync fifo pop underflow 1 - TXR sync fifo pop underflow 2 - TXW hea…
86 …s:R DataWidth:0x6 // 0 - RX target read and config sync fifo push overflow 1 - RX header syn…
[all …]
|
| H A D | reg_addr_k2.h | 9 * or http://opensource.org/licenses/CDDL-1.0.
23 * Copyright 2014-2017 Cavium, Inc.
30 * at http://opensource.org/licenses/CDDL-1.0
39 … 0x001d00UL //Access:R DataWidth:0x2 // Multi Field Register.
44 … 0x001d04UL //Access:RW DataWidth:0x2 // Multi Field Register.
49 … 0x001d08UL //Access:WR DataWidth:0x2 // Multi Field Register.
54 … 0x001d0cUL //Access:RC DataWidth:0x2 // Multi Field Register.
84 …- For ending "endless completion". 0 - When receiving a completion timeout while receiving a compl…
85 … DataWidth:0x4 // 0 - TXCPL sync fifo pop underflow 1 - TXR sync fifo pop underflow 2 - TXW hea…
86 …s:R DataWidth:0x6 // 0 - RX target read and config sync fifo push overflow 1 - RX header syn…
[all …]
|
| H A D | reg_addr_e5.h | 9 * or http://opensource.org/licenses/CDDL-1.0.
23 * Copyright 2014-2017 Cavium, Inc.
30 * at http://opensource.org/licenses/CDDL-1.0
39 … 0x001d00UL //Access:R DataWidth:0x2 // Multi Field Register.
44 … 0x001d04UL //Access:RW DataWidth:0x2 // Multi Field Register.
49 … 0x001d08UL //Access:WR DataWidth:0x2 // Multi Field Register.
54 … 0x001d0cUL //Access:RC DataWidth:0x2 // Multi Field Register.
84 …- For ending "endless completion". 0 - When receiving a completion timeout while receiving a compl…
85 … DataWidth:0x4 // 0 - TXCPL sync fifo pop underflow 1 - TXR sync fifo pop underflow 2 - TXW hea…
86 …s:R DataWidth:0x6 // 0 - RX target read and config sync fifo push overflow 1 - RX header syn…
[all …]
|
| H A D | reg_addr.h | 9 * or http://opensource.org/licenses/CDDL-1.0.
23 * Copyright 2014-2017 Cavium, Inc.
30 * at http://opensource.org/licenses/CDDL-1.0
39 … 0x001d00UL //Access:R DataWidth:0x2 // Multi Field Register.
44 … 0x001d04UL //Access:RW DataWidth:0x2 // Multi Field Register.
49 … 0x001d08UL //Access:WR DataWidth:0x2 // Multi Field Register.
54 … 0x001d0cUL //Access:RC DataWidth:0x2 // Multi Field Register.
85 …- For ending "endless completion". 0 - When receiving a completion timeout while receiving a compl…
86 … DataWidth:0x4 // 0 - TXCPL sync fifo pop underflow 1 - TXR sync fifo pop underflow 2 - TXW hea…
87 …s:R DataWidth:0x6 // 0 - RX target read and config sync fifo push overflow 1 - RX header syn…
[all …]
|
| /freebsd/crypto/openssl/util/ |
| H A D | check-format.pl | 3 # Copyright 2020-2025 The OpenSSL Project Authors. All Rights Reserved.
4 # Copyright Siemens AG 2019-2022
11 # check-format.pl
12 # - check formatting of C source according to OpenSSL coding style
15 # check-format.pl [-l|--strict-len] [-b|--sloppy-bodylen]
16 # [-s|--sloppy-space] [-c|--sloppy-comment]
17 # [-m|--sloppy-macro] [-h|--sloppy-hang]
18 # [-e|--eol-comment] [-1|--1-stmt]
21 # run self-tests:
22 # util/check-format.pl util/check-format-test-positives.c
[all …]
|
| /freebsd/contrib/ofed/opensm/include/complib/ |
| H A D | cl_atomic.h | 2 * Copyright (c) 2004-2006 Voltaire, Inc. All rights reserved.
3 * Copyright (c) 2002-2005 Mellanox Technologies LTD. All rights reserved.
4 * Copyright (c) 1996-2003 Intel Corporation. All rights reserved.
16 * - Redistributions of source code must retain the above
20 * - Redistributions in binary form must reproduce the above
61 * 32-bit signed integers in an atomic fashion.
68 * The cl_atomic_inc function atomically increments a 32-bit signed
77 * [in] Pointer to a 32-bit integer to increment.
87 * synchronization mechanisms in multi-threaded environments.
98 * The cl_atomic_dec function atomically decrements a 32-bit signed
[all …]
|
| /illumos-gate/usr/src/man/man9s/ |
| H A D | tuple.9s | 9 tuple \- card information structure (CIS) access structure
25 The \fBCIS\fR information allows \fBPC\fR cards to be self-identifying: the
33 tuple data structures called a \fBCIS \fRchain. Each tuple has a one-byte type
34 and a one-byte link, an offset to the next tuple in the list. A \fBPC\fR card
38 A multi-function \fBPC\fR card that complies with the \fBPC\fR Card 95
41 \fBPC\fR Cards will also have one or more per-function \fBCIS\fR chains. Each
42 per-function collection of \fBCIS\fR chains is referred to as a
43 function-specific \fBCIS\fR.
56 of the number of tuple-parsing utility functions; for custom tuples, the driver
61 \fRchain a tuple appears in. On a multi-function \fBPC\fR card, the client will
[all …]
|