Home
last modified time | relevance | path

Searched +full:zero +full:- +full:initialised (Results 1 – 17 of 17) sorted by relevance

/Documentation/arm64/
Dbooting.rst13 (EL0 - EL3), with EL0 and EL1 having a secure and a non-secure
14 counterpart. EL2 is the hypervisor level and exists only in non-secure
33 ---------------------------
46 -------------------------
50 The device tree blob (dtb) must be placed on an 8-byte boundary and must
59 ------------------------------
71 ------------------------
75 The decompressed kernel image contains a 64-byte header as follows::
91 - As of v3.17, all fields are little endian unless stated otherwise.
93 - code0/code1 are responsible for branching to stext.
[all …]
/Documentation/arm/
Dporting.rst5 Taken from list archive at http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2001-July/00406…
8 -------------------
14 phys = virt - PAGE_OFFSET + PHYS_OFFSET
18 --------------------
25 to be located in RAM, it can be in flash or other read-only or
26 read-write addressable medium.
29 Start address of zero-initialised work area for the decompressor.
30 This must be pointing at RAM. The decompressor will zero initialise
59 --------------
72 always starts at zero, this is the maximum address that a user
[all …]
/Documentation/networking/
Dz8530book.rst56 shutdown the board. Firstly zero the active field. This ensures nothing
89 Having initialised the device you can then call
92 chip type. If the checks fail to pass the function returns a non zero
95 initialised to either Z8530, Z85C30 or Z85230 according to the chip
113 netdevice field of each channel. The hdlc-> priv field of the network
114 device points to your private data - you will need to be able to find
151 sure to set registers 1-7, 9-11, 14 and 15 in all configurations. Where
176 non zero error status is returned.
185 :c:func:`z8530_sync_dma_open()` function. On failure a non zero
193 ``z8530_sync_txdma_open``. This returns a non zero error code on failure. The
[all …]
Ddccp.txt7 - Introduction
8 - Missing features
9 - Socket options
10 - Sysctl variables
11 - IOCTLs
12 - Other tunables
13 - Notes
20 for real-time and multimedia (streaming) traffic.
24 implementation, this is the TCP-like CCID2 (RFC 4341). Additional CCIDs, such as
25 the TCP-friendly CCID3 (RFC 4342), are optional.
[all …]
/Documentation/filesystems/caching/
Dbackend-api.txt2 FS-CACHE CACHE BACKEND API
5 The FS-Cache system provides an API by which actual caches can be supplied to
6 FS-Cache for it to then serve out to network filesystems and other interested
9 This API is declared in <linux/fscache-cache.h>.
16 To start off, a cache definition must be initialised and registered for each
20 The cache definition (struct fscache_cache) should be initialised by calling:
34 (*) "idfmt" is a format and printf-style arguments for constructing a label
38 The cache should then be registered with FS-Cache by passing a pointer to the
39 previously initialised cache definition to:
47 (*) "fsdef" which should point to the object representation for the FS-Cache
[all …]
/Documentation/devicetree/bindings/regulator/
Dregulator.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Liam Girdwood <lgirdwood@gmail.com>
11 - Mark Brown <broonie@kernel.org>
14 regulator-name:
18 regulator-min-microvolt:
21 regulator-max-microvolt:
24 regulator-microvolt-offset:
27 regulator-min-microamp:
[all …]
/Documentation/admin-guide/blockdev/
Dzram.rst20 There are several ways to configure and manage zram device(-s):
23 b) using zramctl utility, provided by util-linux (util-linux@vger.kernel.org).
28 In order to get a better idea about zramctl please consult util-linux
29 documentation, zramctl man-page or `zramctl --help`. Please be informed
30 that zram maintainers do not develop/maintain util-linux or zramctl, should
31 you have any questions please contact util-linux@vger.kernel.org
45 -EBUSY an attempt to modify an attribute that cannot be changed once
46 the device has been initialised. Please reset device first;
47 -ENOMEM zram was not able to allocate enough memory to fulfil your
49 -EINVAL invalid input has been provided.
[all …]
/Documentation/filesystems/
Dgfs2-glocks.txt2 ------------------------------
10 2. A non-blocking bit lock, GLF_LOCK, which is used to prevent other
28 ------------------------------
40 --------------------------------------------------------------------------
53 ----------------------------------------------------------------------------
86 -------------------------------------------------------------------------
109 5. Transaction glock (via gfs2_trans_begin) for non-read operations
117 is on a per-inode basis. Locking of rgrps is on a per rgrp basis.
121 ------------------
134 The per-glock counters are initialised to zero when the
[all …]
/Documentation/devicetree/bindings/arm/
Dcpus.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
21 with updates for 32-bit and 64-bit ARM systems provided in this document.
30 - square brackets define bitfields, eg reg[7:0] value of the bitfield in
59 On 32-bit ARM v7 or later systems this property is
68 On ARM v8 64-bit systems this property is required
71 * If cpus node's #address-cells property is set to 2
79 * If cpus node's #address-cells property is set to 1
[all …]
/Documentation/networking/device_drivers/3com/
Dvortex.txt16 Linux kernel mailing list <linux-kernel@vger.kernel.org>
22 Since kernel 2.3.99-pre6, this driver incorporates the support for the
23 3c575-series Cardbus cards which used to be handled by 3c575_cb.c.
32 3c595 Vortex 100base-MII
38 3c900B-FL Cyclone 10base-FL
43 3c905B-FX Cyclone 100baseFx
45 3c920B-EMB-WNM (ATI Radeon 9100 IGP)
47 3c980C Python-T
48 3cSOHO100-TX Hurricane
63 3c905B-T4
[all …]
/Documentation/core-api/
Dxarray.rst1 .. SPDX-License-Identifier: GPL-2.0+
15 next or previous entry in a cache-efficient manner. In contrast to a
17 order to grow the array. It is more memory-efficient, parallelisable
18 and cache friendly than a doubly-linked list. It takes advantage of
28 Each non-``NULL`` entry in the array has three bits associated with
32 Normal pointers may be stored in the XArray directly. They must be 4-byte
34 alloc_page(). It isn't true for arbitrary user-space pointers,
60 Storing to any index will store to all of them. Multi-index entries can
69 allocated ones. A freshly-initialised XArray contains a ``NULL``
88 returns ``-EBUSY`` if the entry is not empty.
[all …]
/Documentation/security/keys/
Dcore.rst5 This service allows cryptographic keys, authentication tokens, cross-domain
30 - A serial number.
31 - A type.
32 - A description (for matching a key in a search).
33 - Access control information.
34 - An expiry time.
35 - A payload.
36 - State.
40 the lifetime of that key. All serial numbers are positive non-zero 32-bit
69 the keyring links; in the case of a user-defined key, it's an arbitrary
[all …]
/Documentation/scsi/
Dsym53c8xx_2.txt1 The Linux SYM-2 driver documentation file
5 95170 DEUIL LA BARRE - FRANCE
9 2004-10-09
60 This driver supports the whole SYM53C8XX family of PCI-SCSI controllers.
61 It also support the subset of LSI53C10XX PCI-SCSI controllers that are based
65 with the FreeBSD SYM-2 driver. The `glue' that allows this driver to work
74 Stefan Esser <se@mi.Uni-Koeln.de>
76 1996: port of the ncr driver to Linux-1.2.13 and rename it ncr53c8xx.
84 33 MHz and 66MHz Ultra-3 controllers. The new driver is named `sym'.
110 scsi-config: TCL/Tk tool using scsiinfo
[all …]
Dncr53c8xx.txt5 95170 DEUIL LA BARRE - FRANCE
57 10.4 PCI configuration fix-up boot option
74 16.1 Synchronous timings for 53C875 and 53C860 Ultra-SCSI controllers
75 16.2 Synchronous timings for fast SCSI-2 53C8XX controllers
94 Stefan Esser <se@mi.Uni-Koeln.de>
98 - ncr53c8xx generic driver that supports all the SYM53C8XX family including
101 - sym53c8xx enhanced driver (a.k.a. 896 drivers) that drops support of oldest
107 PCI-HOWTO written by Michael Will and in the SCSI-HOWTO written by
118 Useful SCSI tools written by Eric Youngdale are available at tsx-11:
120 ftp://tsx-11.mit.edu/pub/linux/ALPHA/scsi/scsiinfo-X.Y.tar.gz
[all …]
/Documentation/virt/kvm/
Dapi.txt1 The Definitive KVM (Kernel-based Virtual Machine) API Documentation
5 ----------------------
10 - System ioctls: These query and set global attributes which affect the
14 - VM ioctls: These query and set attributes that affect an entire virtual
21 - vcpu ioctls: These query and set attributes that control the operation
29 - device ioctls: These query and set attributes that control the operation
36 -------------------
73 -------------
77 facility that allows backward-compatible extensions to the API to be
87 ------------------
[all …]
/Documentation/
Dmemory-barriers.txt19 documentation at tools/memory-model/. Nevertheless, even this memory
37 Note also that it is possible that a barrier may be a no-op for an
48 - Device operations.
49 - Guarantees.
53 - Varieties of memory barrier.
54 - What may not be assumed about memory barriers?
55 - Data dependency barriers (historical).
56 - Control dependencies.
57 - SMP barrier pairing.
58 - Examples of memory barrier sequences.
[all …]
/Documentation/driver-api/
Dpinctl.rst9 - Enumerating and naming controllable pins
11 - Multiplexing of pins, pads, fingers (etc) see below for details
13 - Configuration of pins, pads, fingers (etc), such as software-controlled
14 biasing and driving mode specific pins, such as pull-up/down, open drain,
17 Top-level interface
22 - A pin controller is a piece of hardware, usually a set of registers, that
28 - PINS are equal to pads, fingers, balls or whatever packaging input or
32 be sparse - i.e. there may be gaps in the space with numbers where no
98 See for example arch/arm/mach-u300/Kconfig for an example.
197 the groups is up to the driver, this is just a simple example - in practice you
[all …]