Searched +full:boot +full:- +full:partitions (Results 1 – 25 of 45) sorted by relevance
12
| /Documentation/driver-api/mmc/ |
| D | mmc-dev-parts.rst | 2 SD and MMC Device Partitions
5 Device partitions are additional logical block devices present on the
8 As of this writing, MMC boot partitions as supported and exposed as
12 MMC Boot Partitions
15 Read and write access is provided to the two MMC boot partitions. Due to
16 the sensitive nature of the boot partition contents, which often store
21 To enable write access to /dev/mmcblkXbootY, disable the forced read-only
26 To re-enable read-only access::
30 The boot partitions can also be locked read only until the next power on,
36 not support boot partition locking, the file will not exist. If the
[all …]
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| 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 | 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 | 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 | tplink,safeloader-partitions.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mtd/partitions/tplink,safeloader-partitions.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: TP-Link SafeLoader partitions
10 TP-Link home routers store various data on flash (e.g. bootloader,
14 Flash space layout of TP-Link devices is stored on flash itself using
15 a custom ASCII-based format. That format was first found in TP-Link
17 CFE and U-Boot bootloaders.
19 Partitions specified in partitions table cover whole flash space. Some
[all …]
|
| 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 | redboot-fis.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mtd/partitions/redboot-fis.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: RedBoot FLASH Image System (FIS) Partitions
10 format closely associated with the RedBoot boot loader.
17 - Linus Walleij <linus.walleij@linaro.org>
23 const: redboot-fis
25 fis-index-block:
31 '#address-cells': false
[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 | 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 | 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 | orion-nand.txt | 4 - compatible : "marvell,orion-nand".
5 - reg : Base physical address of the NAND and length of memory mapped
9 - cle : Address line number connected to CLE. Default is 0
10 - ale : Address line number connected to ALE. Default is 1
11 - bank-width : Width in bytes of the device. Default is 1
12 - chip-delay : Chip dependent delay for transferring data from array to read
15 The device tree may optionally contain sub-nodes describing partitions of the
21 #address-cells = <1>;
22 #size-cells = <1>;
25 bank-width = <1>;
[all …]
|
| D | nvidia-tegra20-nand.txt | 4 - compatible: Must be one of:
5 - "nvidia,tegra20-nand"
6 - reg: MMIO address range
7 - interrupts: interrupt output of the NFC controller
8 - clocks: Must contain an entry for each entry in clock-names.
9 See ../clocks/clock-bindings.txt for details.
10 - clock-names: Must include the following entries:
11 - nand
12 - resets: Must contain an entry for each entry in reset-names.
14 - reset-names: Must include the following entries:
[all …]
|
| D | lpc32xx-mlc.txt | 4 - compatible: "nxp,lpc3220-mlc"
5 - reg: Address and size of the controller
6 - interrupts: The NAND interrupt specification
7 - gpios: GPIO specification for NAND write protect
13 - nxp,tcea_delay: TCEA_DELAY
14 - nxp,busy_delay: BUSY_DELAY
15 - nxp,nand_ta: NAND_TA
16 - nxp,rd_high: RD_HIGH
17 - nxp,rd_low: RD_LOW
18 - nxp,wr_high: WR_HIGH
[all …]
|
| D | lpc32xx-slc.txt | 4 - compatible: "nxp,lpc3220-slc"
5 - reg: Address and size of the controller
6 - nand-on-flash-bbt: Use bad block table on flash
7 - gpios: GPIO specification for NAND write protect
11 - nxp,wdr-clks: Delay before Ready signal is tested on write (W_RDY)
12 - nxp,rdr-clks: Delay before Ready signal is tested on read (R_RDY)
15 - nxp,wwidth: Write pulse width (W_WIDTH)
16 - nxp,whold: Write hold time (W_HOLD)
17 - nxp,wsetup: Write setup time (W_SETUP)
18 - nxp,rwidth: Read pulse width (R_WIDTH)
[all …]
|
| /Documentation/admin-guide/ |
| D | ldm.rst | 2 LDM - Logical Disk Manager (Dynamic Disks)
5 :Author: Originally Written by FlatCap - Richard Russon <ldm@flatcap.org>.
9 --------
12 replacement for the MSDOS style partitions. It stores its information in a
14 partitions is limited only by disk space. The maximum number of partitions is
17 Any partitions created under the LDM are called "Dynamic Disks". There are no
18 longer any primary or extended partitions. Normal MSDOS style partitions are
23 partitions and filesystems without the need to reboot.
26 assemble any multi-partition volumes, e.g. Stripes, RAID5.
29 dummy MSDOS partition containing one disk-sized partition. This is what is
[all …]
|
| D | iostats.rst | 12 ``/proc/partitions``. In 2.6 and upper, the same information is found in two
37 On 2.4 you might execute ``grep 'hda ' /proc/partitions``. On 2.6+, you have
53 All fields except field 9 are cumulative since boot. Field 9 should
56 or long-lived system; so applications should be prepared to deal with
58 int (32 bit) or unsigned long (32-bit or 64-bit, depending on your
59 machine) as noted per-field below. Unless your observations are very
63 system-wide stats you'll have to find all the devices and sum them all up.
65 Field 1 -- # of reads completed (unsigned long)
68 Field 2 -- # of reads merged, field 6 -- # of writes merged (unsigned long)
74 Field 3 -- # of sectors read (unsigned long)
[all …]
|
| 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
28 by the boot loader; newer kernels use /dev/ram0 for
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
[all …]
|
| /Documentation/tee/ |
| D | ts-tee.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 TS-TEE (Trusted Services project)
10 for developing and deploying device Root of Trust services in FF-A [2] S-EL0
11 Secure Partitions. The project hosts the reference implementation of the Arm
12 Platform Security Architecture [3] for Arm A-profile devices.
14 The FF-A Secure Partitions (SP) are accessible through the FF-A driver [4] which
20 All Trusted Services (TS) SPs have the same FF-A UUID; it identifies the TS RPC
23 present twice in the same SP. During SP boot each service in the SP is assigned
28 OS. However, in case of FF-A, memory sharing works on an endpoint level, i.e.
40 +--------+ +-------------+
[all …]
|
| /Documentation/filesystems/ |
| D | affs.rst | 1 .. SPDX-License-Identifier: GPL-2.0
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.
129 Linux -> Amiga:
[all …]
|
| D | cramfs.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Cramfs - cram a filesystem onto a small ROM
10 allows random page access. The meta-data is not compressed, but is
15 compact also makes it _very_ hard to update on-the-fly), so you have to
20 -----------
36 no need to use -noleaf in ``find``, btw.)
39 (1970 GMT). Recently-accessed files may have updated timestamps, but
52 --------------------------
62 eXecute-In-Place (XIP) from ROM of read-only segments. Data segments mapped
63 read-write (hence they have to be copied to RAM) may still be compressed in
[all …]
|
| /Documentation/arch/arm/sa1100/ |
| D | assabet.rst | 2 The Intel Assabet (SA-1110 evaluation) board
13 -------------------
21 The resulting kernel image should be available in linux/arch/arm/boot/zImage.
25 -----------------------
27 A couple of bootloaders able to boot Linux on Assabet are available:
39 John Dorsey has produced add-on patches to add support for Assabet and
51 Brief examples on how to boot Linux with RedBoot are shown below. But first
55 - ftp://ftp.netwinder.org/users/n/nico/
56 - ftp://ftp.arm.linux.org.uk/pub/linux/arm/people/nico/
57 - ftp://ftp.handhelds.org/pub/linux/arm/sa-1100-patches/
[all …]
|
| /Documentation/scsi/ |
| D | qlogicfas.rst | 1 .. SPDX-License-Identifier: GPL-2.0
15 * IQ-PCI
16 * IQ-PCI-10
17 * IQ-PCI-D
21 Nor does it support the PCI-Basic, which is supported by the
32 can be a simple ctrl-alt-delete with a boot floppy, or by using
60 on a new drive if you want partitions.
|
| /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-
43 (arch/arm/boot/Image). A compressed image can be built by doing a
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
[all …]
|
12