Searched +full:fixed +full:- +full:partitions (Results 1 – 25 of 37) sorted by relevance
12
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | fixed-partitions.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/mtd/partitions/fixed-partitions.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Fixed partitions 12 on-flash partition table such as RedBoot. 14 The partition table should be a node named "partitions". Partitions are then 18 - Rafał Miłecki <rafal@milecki.pl> 23 - const: fixed-partitions 24 - items: [all …]
|
| D | partitions.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/mtd/partitions/partitions.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Partitions 10 This binding is generic and describes the content of the partitions container 14 - Miquel Raynal <miquel.raynal@bootlin.com> 17 - $ref: arm,arm-firmware-suite.yaml 18 - $ref: brcm,bcm4908-partitions.yaml 19 - $ref: brcm,bcm947xx-cfe-partitions.yaml [all …]
|
| D | linux,ubi.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/mtd/partitions/linux,ubi.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 12 physical flash device and spreads the I/O load (i.e wear-leveling) 16 - Daniel Golle <daniel@makrotopia.org> 19 - $ref: partition.yaml# 30 "^ubi-volume-.*$": 31 $ref: /schemas/mtd/partitions/ubi-volume.yaml# 36 - compatible [all …]
|
| D | nvmem-cells.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/mtd/partitions/nvmem-cells.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 Any partition containing the compatible "nvmem-cells" will register as a 13 Nvmem binding to declare nvmem-cells can be found in: 17 - Ansuel Smith <ansuelsmth@gmail.com> 20 - $ref: /schemas/mtd/partitions/partition.yaml# 21 - $ref: /schemas/nvmem/nvmem.yaml# 22 - $ref: /schemas/nvmem/nvmem-deprecated-cells.yaml# [all …]
|
| D | brcm,bcm947xx-cfe-partitions.yaml | 1 # 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# 7 title: Broadcom BCM47xx Partitions 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. 15 Discovering partitions on these devices is possible thanks to having a special 19 Most of partitions use ASCII text based magic for determining a type. More 20 complex partitions (like TRX with its HDR0 magic) may include extra header [all …]
|
| D | brcm,bcm963xx-cfe-nor-partitions.txt | 1 Broadcom BCM963XX CFE Loader NOR Flash Partitions 6 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 12 - compatible : must be "brcm,bcm963xx-cfe-nor-partitions" 17 compatible = "cfi-flash"; 19 bank-width = <2>; 21 partitions { 22 compatible = "brcm,bcm963xx-cfe-nor-partitions";
|
| D | linksys,ns-partitions.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/mtd/partitions/linksys,ns-partitions.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 11 firmware partitions. One is used for regular booting, the other is treated as 14 This binding allows defining all fixed partitions and marking those containing 19 - Rafał Miłecki <rafal@milecki.pl> 25 const: linksys,ns-partitions 27 "#address-cells": 30 "#size-cells": [all …]
|
| D | brcm,bcm4908-partitions.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/mtd/partitions/brcm,bcm4908-partitions.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 Broadcom BCM4908 CFE bootloader supports two firmware partitions. One is used 13 This binding allows defining all fixed partitions and marking those containing 18 - Rafał Miłecki <rafal@milecki.pl> 24 const: brcm,bcm4908-partitions 26 "#address-cells": 29 "#size-cells": [all …]
|
| D | seama.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/mtd/partitions/seama.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Seattle Image Partitions 11 D-Link routers such as DIR-645, DIR-842, DIR-859, DIR-860L, DIR-885L, 12 DIR890L and DCH-M225, as well as in WD and NEC routers on the ath79 18 - $ref: partition.yaml# 21 - Linus Walleij <linus.walleij@linaro.org> 28 - compatible [all …]
|
| D | binman.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/mtd/partitions/binman.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 14 partition. There are quite a number of binman-specific entry types, such as 18 - Simon Glass <sjg@chromium.org> 21 - $ref: /schemas/mtd/partitions/partition.yaml# 26 - u-boot # u-boot.bin from U-Boot project 27 - tfa-bl31 # bl31.bin or bl31.elf from TF-A project 30 - compatible [all …]
|
| D | brcm,bcm963xx-imagetag.txt | 5 partitions or non standard bootloader partition sizes. For these a mixed layout 12 - compatible : must be "brcm,bcm963xx-imagetag" 17 compatible = "cfi-flash"; 19 bank-width = <2>; 21 partitions { 22 compatible = "fixed-partitions"; 23 #address-cells = <1>; 24 #size-cells = <1>; 28 read-only; 33 compatible = "brcm,bcm963xx-imagetag"; [all …]
|
| D | u-boot.yaml | 1 # 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 …]
|
| D | partition.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/mtd/partitions/partition.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 16 Everything after 'partition-' will be used as the partition name to compare 26 - Rafał Miłecki <rafal@milecki.pl> 37 read-only: 39 should only be mounted read-only. This is usually used for flash 40 partitions containing early-boot firmware images or data which should 49 slc-mode: [all …]
|
| /Documentation/devicetree/bindings/nvmem/layouts/ |
| D | u-boot,env.yaml | 1 # 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/devicetree/bindings/mtd/ |
| D | qcom,nandc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> 15 - qcom,ipq806x-nand 16 - qcom,ipq4019-nand 17 - qcom,ipq6018-nand 18 - qcom,ipq8074-nand 19 - qcom,sdx55-nand 26 - description: Core Clock [all …]
|
| D | samsung-s3c2410.txt | 4 - compatible : The possible values are: 5 "samsung,s3c2410-nand" 6 "samsung,s3c2412-nand" 7 "samsung,s3c2440-nand" 8 - reg : register's location and length. 9 - #address-cells, #size-cells : see nand-controller.yaml 10 - clocks : phandle to the nand controller clock 11 - clock-names : must contain "nand" 17 - nand-ecc-mode : see nand-controller.yaml 18 - nand-on-flash-bbt : see nand-controller.yaml [all …]
|
| D | ingenic,nand.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Paul Cercueil <paul@crapouillou.net> 13 - $ref: nand-controller.yaml# 14 - $ref: /schemas/memory-controllers/ingenic,nemc-peripherals.yaml# 19 - ingenic,jz4740-nand 20 - ingenic,jz4725b-nand 21 - ingenic,jz4780-nand 25 - description: Bank number, offset and size of first attached NAND chip [all …]
|
| D | mediatek,mtk-nfc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/mtd/mediatek,mtk-nfc.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Xiangsheng Hou <xiangsheng.hou@mediatek.com> 15 - mediatek,mt2701-nfc 16 - mediatek,mt2712-nfc 17 - mediatek,mt7622-nfc 21 - description: Base physical address and size of NFI. 25 - description: NFI interrupt [all …]
|
| D | marvell,nand-controller.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/mtd/marvell,nand-controller.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Miquel Raynal <miquel.raynal@bootlin.com> 15 - items: 16 - const: marvell,armada-8k-nand-controller 17 - const: marvell,armada370-nand-controller 18 - enum: 19 - marvell,ac5-nand-controller [all …]
|
| /Documentation/filesystems/ |
| D | affs.rst | 1 .. SPDX-License-Identifier: GPL-2.0 18 a bug has been fixed so that accented ("international") letters 19 in file names are case-insensitive, as they ought to be. 107 Amiga -> Linux: 111 - R maps to r for user, group and others. On directories, R implies x. 113 - W maps to w. 115 - E maps to x. 117 - D is ignored. 119 - H, S and P are always retained and ignored under Linux. 121 - A is cleared when a file is written to. [all …]
|
| D | hpfs.rst | 1 .. SPDX-License-Identifier: GPL-2.0 7 1998-2004, Mikulas Patocka 10 :homepage: https://artax.karlin.mff.cuni.cz/~mikulas/vyplody/hpfs/index-e.cgi 14 Chris Smith, 1993, original read-only HPFS, some code and hpfs structures file 25 attributes. Mode is inverted umask - for example umask 027 gives owner 32 CR/LF -> LF conversion, if auto, decision is made according to extension 33 - there is a list of text extensions (I thing it's better to not convert 43 corrupted filesystems. check=strict means many superfluous checks - 46 errors=continue,remount-ro,panic (default remount-ro) 51 What to do with extended attributes. 'no' - ignore them and use always [all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | marvell,aquantia.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Christian Marangi <ansuelsmth@gmail.com> 17 - Attached SPI flash directly to the PHY with the firmware. The PHY 19 - Read from a dedicated partition on system NAND declared in an 21 - Manually provided firmware loaded from a file in the filesystem. 24 - $ref: ethernet-phy.yaml# 31 - ethernet-phy-id03a1.b445 32 - ethernet-phy-id03a1.b460 [all …]
|
| /Documentation/admin-guide/ |
| D | devices.txt | 1 0 Unnamed devices (e.g. non-device mounts) 7 2 = /dev/kmem OBSOLETE - replaced by /proc/kcore 11 6 = /dev/core OBSOLETE - replaced by /proc/kcore 18 12 = /dev/oldmem OBSOLETE - replaced by /proc/vmcore 31 2 char Pseudo-TTY masters 37 Pseudo-tty's are named as follows: 40 the 1st through 16th series of 16 pseudo-ttys each, and 44 These are the old-style (BSD) PTY devices; Unix98 106 3 char Pseudo-TTY slaves 112 These are the old-style (BSD) PTY devices; Unix98 [all …]
|
| /Documentation/scsi/ |
| D | st.rst | 1 .. SPDX-License-Identifier: GPL-2.0 23 flexible method and applicable to single-user workstations. However, 32 drive performs auto-detection of the tape format well (like some 33 QIC-drives). The result is that any tape can be read, writing can be 37 does not perform auto-detection well enough and there is a single 40 or not :-). 57 between formats in multi-tape operations (the explicitly overridden 71 The driver supports fixed and variable block size (within buffer 72 limits). Both the auto-rewind (minor equals device number) and 73 non-rewind devices (minor is 128 + device number) are implemented. [all …]
|
| /Documentation/arch/arm/ |
| D | arm.rst | 9 --------------------- 21 If you wish to cross-compile, then alter the following lines in the top 36 CROSS_COMPILE=<your-path-to-your-compiler-without-gcc> 40 CROSS_COMPILE=arm-linux- 48 --------------- 54 Bug reports should be sent to linux-arm-kernel@lists.arm.linux.org.uk, 64 ------------- 66 Several new include directories have been created under include/asm-arm, 67 which are there to reduce the clutter in the top-level directory. These 71 `arch-*` machine/platform specific header files [all …]
|
12