Home
last modified time | relevance | path

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

12

/Documentation/filesystems/
Daffs.txt14 a bug has been fixed so that accented ("international") letters
15 in file names are case-insensitive, as they ought to be.
79 symbolic links on an AFFS partition. Default = "/".
82 volume=name When symbolic links with an absolute path are created
90 Amiga -> Linux:
94 - R maps to r for user, group and others. On directories, R implies x.
96 - If both W and D are allowed, w will be set.
98 - E maps to x.
100 - H and P are always retained and ignored under Linux.
102 - A is always reset when a file is written to.
[all …]
Docfs2-online-filecheck.txt2 -----------------------
8 OCFS2 is often used in high-availability systems. However, OCFS2 usually
9 converts the filesystem to read-only when encounters an error. This may not be
10 necessary, since turning the filesystem read-only would affect other running
13 -EIO errno to the calling process and terminate further processing so that the
15 read-only, and the problematic file's inode number is reported in the kernel
20 This effort is to check/fix small issues which may hinder day-to-day operations
21 of a cluster filesystem by turning the filesystem read-only. The scope of
25 In case of directory to file links is incorrect, the directory inode is
50 fixed. Currently, three operations are supported, which includes checking
[all …]
Dqnx6.txt24 ------
26 The space in the device or file is split up into blocks. These are a fixed
33 ---------------
58 Unused block pointers are always set to ~0 - regardless of root node,
70 0x1000 is the size reserved for each superblock - regardless of the
74 ------
94 -----------
110 -------------
112 Symbolic links are also filesystem objects with inodes. They got a specific
116 Hard links got an inode, a directory entry, but a specific mode bit set,
[all …]
Dext2.txt15 set using tune2fs(8). Kernel-determined defaults are indicated by (*).
30 errors=remount-ro Remount the filesystem read-only on an error.
36 nouid32 Use 16-bit UIDs and GIDs.
81 ------
84 a fixed size, of 1024, 2048 or 4096 bytes (8192 bytes on Alpha systems),
90 ------------
107 --------------
137 ------
145 modification time, deletion time, number of links, fragments, version
161 pointers to the next set of blocks), a pointer to a doubly-indirect
[all …]
Dramfs-rootfs-initramfs.txt7 --------------
11 RAM-based filesystem.
34 ------------------
38 device was of fixed size, so the filesystem mounted on it was of fixed
52 Another reason ramdisks are semi-obsolete is that the introduction of
58 ----------------
71 ---------------
87 ------------------
101 - The old initrd was always a separate file, while the initramfs archive is
102 linked into the linux kernel image. (The directory linux-*/usr is devoted
[all …]
/Documentation/sound/soc/
Ddpcm.rst18 DPCM re-uses all the existing component codec, platform and DAI drivers without
23 -------------------------------------
26 document for all examples :-
32 PCM0 <------------> * * <----DAI0-----> Codec Headset
34 PCM1 <------------> * * <----DAI1-----> Codec Speakers
36 PCM2 <------------> * * <----DAI2-----> MODEM
38 PCM3 <------------> * * <----DAI3-----> BT
40 * * <----DAI4-----> DMIC
42 * * <----DAI5-----> FM
53 Example - DPCM Switching playback from DAI0 to DAI1
[all …]
/Documentation/networking/
Dsfp-phylink.rst1 .. SPDX-License-Identifier: GPL-2.0
10 phylink is a mechanism to support hot-pluggable networking modules
11 directly connected to a MAC without needing to re-initialise the
12 adapter on hot-plug events.
14 phylink supports conventional phylib-based setups, fixed link setups
30 2. Fixed mode
32 Fixed mode is the same as PHY mode as far as the MAC driver is
35 3. In-band mode
37 In-band mode is used with 802.3z, SGMII and similar interface modes,
38 and we are expecting to use and honor the in-band negotiation or
[all …]
Dkapi.rst9 ---------------------
11 .. kernel-doc:: include/linux/net.h
15 -----------------------
17 .. kernel-doc:: include/linux/skbuff.h
20 .. kernel-doc:: include/net/sock.h
23 .. kernel-doc:: net/socket.c
26 .. kernel-doc:: net/core/skbuff.c
29 .. kernel-doc:: net/core/sock.c
32 .. kernel-doc:: net/core/datagram.c
35 .. kernel-doc:: net/core/stream.c
[all …]
Dbonding.txt7 Corrections, HA extensions : 2000/10/03-15 :
8 - Willy Tarreau <willy at meta-x.org>
9 - Constantine Gavrilov <const-g at xpert.com>
10 - Chad N. Tindel <ctindel at ieee dot org>
11 - Janice Girouard <girouard at us dot ibm dot com>
12 - Jay Vosburgh <fubar at us dot ibm dot com>
16 - Mitch Williams <mitch.a.williams at intel.com>
29 the original tools from extreme-linux and beowulf sites will not work
33 who to ask for help, please follow the links at the end of this file.
101 16. Resources and Links
[all …]
/Documentation/admin-guide/
Dsysfs-rules.rst4 The kernel-exported sysfs exports internal kernel implementation details
11 low-level userspace applications, with a new kernel release, the users
12 of sysfs must follow some rules to use an as-abstract-as-possible way to
21 - Do not use libsysfs
23 offer any abstraction, it exposes all the kernel driver-core
31 - sysfs is always at ``/sys``
38 - devices are only "devices"
39 There is no such thing like class-, bus-, physical devices,
41 just simply a "device". Class-, bus-, physical, ... types are just
47 - devpath (``/devices/pci0000:00/0000:00:1d.1/usb2/2-2/2-2:1.0``)
[all …]
Dthunderbolt.rst5 should be a userspace tool that handles all the low-level details, keeps
9 found in ``Documentation/ABI/testing/sysfs-bus-thunderbolt``.
13 ``/etc/udev/rules.d/99-local.rules``::
22 -----------------------------------
57 Display Port in a dock. All PCIe links downstream of the dock are
75 -----------------------------------------------------------------
78 /sys/bus/thunderbolt/devices/0-1/authorized - 0
79 /sys/bus/thunderbolt/devices/0-1/device - 0x8004
80 /sys/bus/thunderbolt/devices/0-1/device_name - Thunderbolt to FireWire Adapter
81 /sys/bus/thunderbolt/devices/0-1/vendor - 0x1
[all …]
/Documentation/devicetree/bindings/net/
Dethernet-controller.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/net/ethernet-controller.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - David S. Miller <davem@davemloft.net>
16 local-mac-address:
18 - $ref: /schemas/types.yaml#definitions/uint8-array
19 - items:
20 - minItems: 6
25 mac-address:
[all …]
/Documentation/media/uapi/v4l/
Dvidioc-subdev-enum-frame-size.rst4 .. Foundation, with no Invariant Sections, no Front-Cover Texts
5 .. and no Back-Cover Texts. A copy of the license is included at
6 .. Documentation/media/uapi/fdl-appendix.rst.
8 .. TODO: replace it to GFDL-1.1-or-later WITH no-invariant-sections
19 VIDIOC_SUBDEV_ENUM_FRAME_SIZE - Enumerate media bus frame sizes
33 File descriptor returned by :ref:`open() <func-open>`.
43 a sub-device on the given pad for the given media bus format. Supported
55 Sub-devices that only support discrete frame sizes (such as most
60 supported. For instance, a scaler that uses a fixed-point scaling ratio
64 sub-device for an exact supported frame size.
[all …]
/Documentation/devicetree/
Dwriting-schema.rst3 Writing DeviceTree Bindings in json-schema
6 Devicetree bindings are written using json-schema vocabulary. Schema files are
12 ---------------
14 Each schema doc is a structured json-schema which is defined by a set of
15 top-level properties. Generally, there is one binding defined per file. The
16 top-level json-schema properties used are:
19 A json-schema unique identifier string. The string must be a valid
29 Indicates the meta-schema the schema file adheres to.
39 Optional. A multi-line text block containing any detailed
41 or device does, standards the device conforms to, and links to datasheets for
[all …]
/Documentation/media/v4l-drivers/
Dimx.rst1 .. SPDX-License-Identifier: GPL-2.0
7 ------------
15 - Image DMA Controller (IDMAC)
16 - Camera Serial Interface (CSI)
17 - Image Converter (IC)
18 - Sensor Multi-FIFO Controller (SMFC)
19 - Image Rotator (IRT)
20 - Video De-Interlacing or Combining Block (VDIC)
26 re-ordering (for example UYVY to YUYV) within the same colorspace, and
27 packed <--> planar conversion. The IDMAC can also perform a simple
[all …]
/Documentation/networking/device_drivers/dec/
Dde4x5.txt42 measurement. Their error is +/-20k on a quiet (private) network and also
59 2) for fixed autoprobes (not recommended), edit the source code near
73 3) compile de4x5.c, but include -DMODULE in the command line to ensure
105 The SMC9332 card has a non-compliant SROM which needs fixing - I have
107 to a previous DEC-STD format.
134 interrupt service code is fixed. YOU SHOULD SEPARATE OUT THE FAST
138 Finally, I think I have really fixed the module loading problem with
147 SROM, the feature is ignored unless lp->params.fdx is set at compile
150 duplex links except through autonegotiation. When I include the
156 and media. The only lexical constraints are: the board name (dev->name)
[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/devicetree/bindings/display/msm/
Ddsi.txt5 - compatible:
6 * "qcom,mdss-dsi-ctrl"
7 - reg: Physical base address and length of the registers of controller
8 - reg-names: The names of register regions. The following regions are required:
10 - interrupts: The interrupt signal from the DSI block.
11 - power-domains: Should be <&mmcc MDSS_GDSC>.
12 - clocks: Phandles to device clocks.
13 - clock-names: the following clocks are required:
25 - assigned-clocks: Parents of "byte" and "pixel" for the given platform.
26 - assigned-clock-parents: The Byte clock and Pixel clock PLL outputs provided
[all …]
/Documentation/devicetree/bindings/sound/
Dsimple-card.txt1 Simple-Card:
3 Simple-Card specifies audio DAI connections of SoC <-> codec.
7 - compatible : "simple-audio-card"
11 - simple-audio-card,name : User specified audio sound card name, one string
13 - simple-audio-card,widgets : Please refer to widgets.txt.
14 - simple-audio-card,routing : A list of the connections between audio components.
18 - simple-audio-card,mclk-fs : Multiplication factor between stream rate and codec
19 mclk. When defined, mclk-fs property defined in
20 dai-link sub nodes are ignored.
21 - simple-audio-card,hp-det-gpio : Reference to GPIO that signals when
[all …]
/Documentation/scsi/
Dst.txt16 flexible method and applicable to single-user workstations. However,
25 drive performs auto-detection of the tape format well (like some
26 QIC-drives). The result is that any tape can be read, writing can be
30 does not perform auto-detection well enough and there is a single
33 or not :-).
50 between formats in multi-tape operations (the explicitly overridden
64 The driver supports fixed and variable block size (within buffer
65 limits). Both the auto-rewind (minor equals device number) and
66 non-rewind devices (minor is 128 + device number) are implemented.
73 In fixed block mode, the data transfer between the drive and the
[all …]
/Documentation/driver-api/soundwire/
Dsummary.rst10 SoundWire is a 2-pin multi-drop interface with data and clock line. It
15 commands over a single two-pin interface.
23 (4) Device status monitoring, including interrupt-style alerts to the Master.
30 transmit or receiving mode (typically fixed direction but configurable
38 +---------------+ +---------------+
40 | Master |-------+-------------------------------| Slave |
42 | |-------|-------+-----------------------| |
43 +---------------+ | | +---------------+
47 +--+-------+--+
52 +-------------+
[all …]
/Documentation/driver-api/driver-model/
Ddriver.rst43 model because the bus they belong to has a bus-specific structure with
44 bus-specific fields that cannot be generalized.
49 completely bus-specific. Defining them as bus-specific entities would
50 sacrifice type-safety, so we keep bus-specific structures around.
52 Bus-specific drivers should include a generic struct device_driver in
53 the definition of the bus-specific driver. Like this::
60 A definition that included bus-specific fields would look like
86 no bus-specific fields (i.e. don't have a bus-specific driver
90 Most drivers, however, will have a bus-specific structure and will
106 define generic callbacks that forward the call to the bus-specific
[all …]
/Documentation/networking/dsa/
Ddsa.rst22 An Ethernet switch is typically comprised of multiple front-panel ports, and one
27 gateways, or even top-of-the rack switches. This host Ethernet controller will
32 using upstream and downstream Ethernet links between switches. These specific
36 For each front-panel port, DSA will create specialized network devices which are
37 used as controlling and data-flowing endpoints for use by the Linux networking
46 - what port is this frame coming from
47 - what was the reason why this frame got forwarded
48 - how to send CPU originated traffic to specific ports
52 on Port-based VLAN IDs).
57 - the "cpu" port is the Ethernet switch facing side of the management
[all …]
/Documentation/vm/
Dfrontswap.rst9 swapped pages are saved in RAM (or a RAM-like device) instead of a swap disk.
11 (Note, frontswap -- and :ref:`cleancache` (merged at 3.0) -- are the "frontends"
13 all other supporting code -- the "backends" -- is implemented as drivers.
21 a synchronous concurrency-safe page-oriented "pseudo-RAM device" conforming
23 in-kernel compressed memory, aka "zcache", or future RAM-like devices);
24 this pseudo-RAM device is not directly accessible or addressable by the
25 kernel and is of unknown and possibly time-varying size. The driver
26 links itself to frontswap by calling frontswap_register_ops to set the
50 in swap device writes is lost (and also a non-trivial performance advantage)
88 useful for write-balancing for some RAM-like devices). Swap pages (and
[all …]
/Documentation/arm64/
Darm-acpi.rst12 5.1 or later. Links to the specification and all external documents
22 industry-standard ARMv8 servers, they also apply to more than one operating
24 ACPI and Linux only, on an ARMv8 system -- that is, what Linux expects of
29 ----------------
32 exist in Linux for describing non-enumerable hardware, after all. In this
39 - ACPI’s byte code (AML) allows the platform to encode hardware behavior,
44 - ACPI’s OSPM defines a power management model that constrains what the
48 - In the enterprise server environment, ACPI has established bindings (such
54 - Choosing a single interface to describe the abstraction between a platform
60 - The new ACPI governance process works well and Linux is now at the same
[all …]

12