Home
last modified time | relevance | path

Searched +full:fixed +full:- +full:header (Results 1 – 25 of 139) sorted by relevance

123456

/Documentation/netlink/specs/
Dnftables.yaml1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
4 protocol: netlink-raw
11 -
15 -
16 name: nfgen-family
18 -
21 -
22 name: res-id
23 byte-order: big-endian
25 -
[all …]
Dtc.yaml1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
4 protocol: netlink-raw
12 -
16 -
19 -
23 -
26 -
29 -
32 -
35 -
[all …]
Drt_route.yaml1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
3 name: rt-route
4 protocol: netlink-raw
11 -
12 name: rtm-type
13 name-prefix: rtn-
16 - unspec
17 - unicast
18 - local
19 - broadcast
[all …]
Dovs_datapath.yaml1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
5 protocol: genetlink-legacy
6 uapi-header: linux/openvswitch.h
12 -
13 name: ovs-header
16 -
17 name: dp-ifindex
19 -
20 name: user-features
22 name-prefix: ovs-dp-f-
[all …]
Dovs_vport.yaml1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
5 protocol: genetlink-legacy
6 uapi-header: linux/openvswitch.h
12 -
13 name: ovs-header
16 -
17 name: dp-ifindex
19 -
20 name: vport-type
22 enum-name: ovs-vport-type
[all …]
/Documentation/networking/
Dradiotap-headers.rst1 .. SPDX-License-Identifier: GPL-2.0
8 ------------------------------------
10 Radiotap headers are variable-length and extensible, you can get most of the
18 Structure of the header
19 -----------------------
21 There is a fixed portion at the start which contains a u32 bitmap that defines
24 the header for argument index 0 (IEEE80211_RADIOTAP_TSFT) is present in the
29 < 8-byte ieee80211_radiotap_header >
44 --------------------------
46 After the fixed part of the header, the arguments follow for each argument
[all …]
/Documentation/userspace-api/netlink/
Dgenetlink-legacy.rst1 .. SPDX-License-Identifier: BSD-3-Clause
9 the ``genetlink-legacy`` protocol level.
15 -------
29 --------------------
31 New Netlink families should use ``multi-attr`` to define arrays.
35 For reference the ``multi-attr`` array may look like this::
37 [ARRAY-ATTR]
41 [SOME-OTHER-ATTR]
42 [ARRAY-ATTR]
47 where ``ARRAY-ATTR`` is the array entry type.
[all …]
Dnetlink-raw.rst1 .. SPDX-License-Identifier: BSD-3-Clause
8 families such as ``NETLINK_ROUTE`` which use the ``netlink-raw`` protocol
14 The netlink-raw schema extends the :doc:`genetlink-legacy <genetlink-legacy>`
17 information. The raw netlink families also make use of type-specific
18 sub-messages.
21 -------
29 .. code-block:: yaml
31 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
33 name: rt-addr
34 protocol: netlink-raw
[all …]
Dintro.rst1 .. SPDX-License-Identifier: BSD-3-Clause
8 It aims to replace fixed-format C structures as supplied
12 To achieve this Netlink uses a minimal fixed-format metadata header
27 .. code-block:: c
39 .. code-block:: c
52 .. code-block:: c
69 The first two arguments of the socket() call require little explanation -
76 --------------------------
82 file, they include among others - general networking (NETLINK_ROUTE),
100 In addition to the Netlink fixed metadata header each Netlink protocol
[all …]
/Documentation/netlink/
Dnetlink-raw.yaml1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
3 ---
4 $id: http://kernel.org/schemas/netlink/netlink-raw.yaml#
5 $schema: https://json-schema.org/draft-07/schema
12 len-or-define:
14 pattern: ^[0-9A-Za-z_-]+( - 1)?$
21 required: [ name, doc, attribute-sets, operations ]
31 enum: [ netlink-raw ] # Trim
32 # Start netlink-raw
34 description: Protocol number to use for netlink-raw
[all …]
Dgenetlink-legacy.yaml1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
3 ---
4 $id: http://kernel.org/schemas/netlink/genetlink-legacy.yaml#
5 $schema: https://json-schema.org/draft-07/schema
12 len-or-define:
14 pattern: ^[0-9A-Za-z_-]+( - 1)?$
16 len-or-limit:
17 # literal int or limit based on fixed-width type e.g. u8-min, u16-max, etc.
19 pattern: ^[su](8|16|32|64)-(min|max)$
26 required: [ name, doc, attribute-sets, operations ]
[all …]
/Documentation/devicetree/bindings/mtd/partitions/
Dbrcm,bcm947xx-cfe-partitions.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mtd/partitions/brcm,bcm947xx-cfe-partitions.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
12 partitions without any on-flash partition table. On some devices their sizes
13 and/or meanings can also vary so fixed partitioning can't be used.
16 header and/or magic signature at the beginning of each of them. They are also
20 complex partitions (like TRX with its HDR0 magic) may include extra header
32 same TRX format with the same header. To distinguish currently used firmware a
36 - Rafał Miłecki <rafal@milecki.pl>
[all …]
Dbrcm,bcm963xx-cfe-nor-partitions.txt6 NVRAM partition, and the remainder in-between for one to two firmware partitions
7 at fixed offsets. A valid firmware partition is identified by the ImageTag
8 header found at beginning of the second erase block, containing the rootfs and
12 - compatible : must be "brcm,bcm963xx-cfe-nor-partitions"
17 compatible = "cfi-flash";
19 bank-width = <2>;
22 compatible = "brcm,bcm963xx-cfe-nor-partitions";
Dbrcm,bcm963xx-imagetag.txt8 The BCM963XX ImageTag is a simple firmware header describing the offsets and
12 - compatible : must be "brcm,bcm963xx-imagetag"
17 compatible = "cfi-flash";
19 bank-width = <2>;
22 compatible = "fixed-partitions";
23 #address-cells = <1>;
24 #size-cells = <1>;
28 read-only;
33 compatible = "brcm,bcm963xx-imagetag";
38 read-only;
Du-boot.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mtd/partitions/u-boot.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: U-Boot bootloader partition
10 U-Boot is a bootloader commonly used in embedded devices. It's almost always
17 - Rafał Miłecki <rafal@milecki.pl>
20 - $ref: partition.yaml#
25 - const: brcm,u-boot
27 Broadcom stores environment variables inside a U-Boot partition. They
[all …]
/Documentation/devicetree/bindings/clock/
Dsamsung,s5pv210-clock.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/clock/samsung,s5pv210-clock.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Chanwoo Choi <cw00.choi@samsung.com>
11 - Krzysztof Kozlowski <krzk@kernel.org>
12 - Sylwester Nawrocki <s.nawrocki@samsung.com>
13 - Tomasz Figa <tomasz.figa@gmail.com>
16 Expected external clocks, defined in DTS as fixed-rate clocks with a matching
18 - "xxti" - external crystal oscillator connected to XXTI and XXTO pins of
[all …]
Dsamsung,s5pv210-audss-clock.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/clock/samsung,s5pv210-audss-clock.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Chanwoo Choi <cw00.choi@samsung.com>
11 - Krzysztof Kozlowski <krzk@kernel.org>
12 - Sylwester Nawrocki <s.nawrocki@samsung.com>
13 - Tomasz Figa <tomasz.figa@gmail.com>
17 include/dt-bindings/clock/s5pv210-audss.h header.
21 const: samsung,s5pv210-audss-clock
[all …]
Dsamsung,exynos5410-clock.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/clock/samsung,exynos5410-clock.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Chanwoo Choi <cw00.choi@samsung.com>
11 - Krzysztof Kozlowski <krzk@kernel.org>
12 - Sylwester Nawrocki <s.nawrocki@samsung.com>
13 - Tomasz Figa <tomasz.figa@gmail.com>
16 Expected external clocks, defined in DTS as fixed-rate clocks with a matching
18 - "fin_pll" - PLL input clock from XXTI
[all …]
Dmaxim,max9485.txt5 - MAX9485_MCLKOUT: A gated, buffered output of the input clock of 27 MHz
6 - MAX9485_CLKOUT: A PLL that can be configured to 16 different discrete
8 - MAX9485_CLKOUT[1,2]: Two gated outputs for MAX9485_CLKOUT
14 - compatible: "maxim,max9485"
15 - clocks: Input clock, must provide 27.000 MHz
16 - clock-names: Must be set to "xclk"
17 - #clock-cells: From common clock binding; shall be set to 1
20 - reset-gpios: GPIO descriptor connected to the #RESET input pin
21 - vdd-supply: A regulator node for Vdd
22 - clock-output-names: Name of output clocks, as defined in common clock
[all …]
/Documentation/devicetree/bindings/nvmem/layouts/
Du-boot,env.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/nvmem/layouts/u-boot,env.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: U-Boot environment variables layout
10 U-Boot uses environment variables to store device parameters and
14 Data is stored using U-Boot specific formats (variant specific header and NUL
15 separated key-value pairs).
27 - Rafał Miłecki <rafal@milecki.pl>
32 - description: A standalone env data block
[all …]
/Documentation/admin-guide/media/
Drcar-fdp1.rst1 .. SPDX-License-Identifier: GPL-2.0
3 Renesas R-Car Fine Display Processor (FDP1) Driver
6 The R-Car FDP1 driver implements driver-specific controls as follows.
9 The video deinterlacing mode (such as Bob, Weave, ...). The R-Car FDP1
12 .. flat-table::
13 :header-rows: 0
14 :stub-columns: 0
17 * - ``"Progressive" (0)``
18 - The input image video stream is progressive (not interlaced). No
21 * - ``"Adaptive 2D/3D" (1)``
[all …]
/Documentation/security/
Ddigsig.rst13 3. User-space utilities
22 Digital signature verification is implemented using cut-down kernel port of
23 GnuPG multi-precision integers (MPI) library. The kernel port provides
25 coding style, and checkpatch.pl reported errors and warnings have been fixed.
27 Public key and signature consist of header and MPIs::
47 keyid equals to SHA1[12-19] over the total key content.
48 Signature header is used as an input to generate a signature.
49 Such approach insures that key or signature header could not be changed.
58 digsig_verify() - digital signature verification with public key
62 * digsig_verify() - digital signature verification with public key
[all …]
/Documentation/arch/sparc/oradax/
Ddax-hv-api.txt3 Publication date 2017-09-25 08:21
5 Extracted via "pdftotext -f 547 -l 572 -layout sun4v_20170925.pdf"
16 live-migration and other system management activities.
20 …high speed processoring of database-centric operations. The coprocessors may support one or more of
28 …e Completion Area and, unless execution order is specifically restricted through the use of serial-
38 …There is no fixed limit on the number of outstanding CCBs guest software may have queued in the vi…
45 …device node in the guest MD (Section 8.24.17, “Database Analytics Accelerators (DAX) virtual-device
51 36.1.1.1. "ORCL,sun4v-dax" Device Compatibility
54 • No-op/Sync
81 36.1.1.2. "ORCL,sun4v-dax-fc" Device Compatibility
[all …]
/Documentation/filesystems/ext4/
Dinodes.rst1 .. SPDX-License-Identifier: GPL-2.0
4 -----------
15 links and is in general more seek-happy than ext4 due to its simpler
22 ``(inode_number - 1) / sb.s_inodes_per_group``, and the offset into the
23 group's table is ``(inode_number - 1) % sb.s_inodes_per_group``. There
31 .. list-table::
33 :header-rows: 1
36 * - Offset
37 - Size
38 - Name
[all …]
/Documentation/virt/gunyah/
Dmessage-queue.rst1 .. SPDX-License-Identifier: GPL-2.0
5 Message queue is a simple low-capacity IPC channel between two virtual machines.
7 message queue is unidirectional and buffered in the hypervisor. A full-duplex
11 fixed at creation of the message queue. Resource manager is presently the only
13 with a fixed maximum message size of 240 bytes. Longer messages require a
15 communication with the resource manager adds a header field for sending longer
32 queue is being used to implement an RPC-like interface.
44 Clear-to-Send.
52 +-------------------+ +-----------------+ +-------------------+
57 | |-------->| | Rx vIRQ | |
[all …]

123456