| /freebsd/sys/contrib/device-tree/Bindings/mtd/partitions/ |
| H A D | fixed-partitions.yaml | 4 $id: http://devicetree.org/schemas/mtd/partitions/fixed-partitions.yaml#
7 title: Fixed partitions
14 The partition table should be a node named "partitions". Partitions are then
23 - const: fixed-partitions
25 - const: sercomm,sc-partitions
26 - const: fixed-partitions
72 partitions {
73 compatible = "fixed-partitions";
[all...] |
| H A D | tplink,safeloader-partitions.yaml | 4 $id: http://devicetree.org/schemas/mtd/partitions/tplink,safeloader-partitions.yaml#
7 title: TP-Link SafeLoader partitions
19 Partitions specified in partitions table cover whole flash space. Some
22 partitions contain fully changeable content (like rootfs).
25 based partitions table. That offset is picked at manufacturing process
33 const: tplink,safeloader-partitions
35 partitions-table-offset:
36 description: Flash offset of partitions table
44 - partitions-table-offset
50 partitions {
[all …]
|
| H A D | brcm,bcm947xx-cfe-partitions.txt | 1 Broadcom BCM47xx Partitions
5 home routers. Their BCM947xx boards using CFE bootloader have several partitions
9 Discovering partitions on these devices is possible thanks to having a special
13 Most of partitions use ASCII text based magic for determining a type. More
14 complex partitions (like TRX with its HDR0 magic) may include extra header
17 A list of supported partitions includes:
24 As mentioned earlier, role of some partitions may depend on extra configuration.
30 Devices using Broadcom partitions described above should should have flash node
31 with a subnode named "partitions" using following properties:
34 - compatible : (required) must be "brcm,bcm947xx-cfe-partitions"
[all …]
|
| H A D | brcm,bcm947xx-cfe-partitions.yaml | 4 $id: http://devicetree.org/schemas/mtd/partitions/brcm,bcm947xx-cfe-partitions.yaml#
7 title: Broadcom BCM47xx Partitions
12 partitions without any on-flash partition table. On some devices their sizes
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
23 A list of supported partitions includes:
30 As mentioned earlier, role of some partitions may depend on extra
42 const: brcm,bcm947xx-cfe-partitions
48 partitions {
[all …]
|
| H A D | partitions.yaml | 4 $id: http://devicetree.org/schemas/mtd/partitions/partitions.yaml#
7 title: Partitions
10 This binding is generic and describes the content of the partitions container
18 - $ref: brcm,bcm4908-partitions.yaml
19 - $ref: brcm,bcm947xx-cfe-partitions.yaml
20 - $ref: fixed-partitions.yaml
21 - $ref: linksys,ns-partitions.yaml
24 - $ref: tplink,safeloader-partitions.yaml
|
| H A D | brcm,trx.txt | 9 identification fields, CRC32 checksum and the locations of embedded partitions.
10 Its purpose is to store a few partitions in a format that can be distributed as
13 Container can hold up to 4 partitions. The first partition has to contain a
15 executing. Other partitions can be used for operating system purposes. This is
19 partitions have to be less than the 4GiB max size limit.
22 1) v1 which contains 3 partitions
23 2) v2 which contains 4 partitions
39 partitions {
|
| H A D | linksys,ns-partitions.yaml | 4 $id: http://devicetree.org/schemas/mtd/partitions/linksys,ns-partitions.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
25 const: linksys,ns-partitions
51 partitions {
52 compatible = "linksys,ns-partitions";
|
| H A D | brcm,bcm4908-partitions.yaml | 4 $id: http://devicetree.org/schemas/mtd/partitions/brcm,bcm4908-partitions.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
24 const: brcm,bcm4908-partitions
48 partitions {
49 compatible = "brcm,bcm4908-partitions";
|
| H A D | qcom,smem-part.yaml | 4 $id: http://devicetree.org/schemas/mtd/partitions/qcom,smem-part.yaml#
14 Memory (SMEM) based partition table scheme. The maximum partitions supported
15 varies between partition table revisions. V3 supports maximum 16 partitions
16 and V4 supports 48 partitions.
36 partitions {
44 partitions {
|
| H A 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
12 - compatible : must be "brcm,bcm963xx-cfe-nor-partitions"
21 partitions {
22 compatible = "brcm,bcm963xx-cfe-nor-partitions";
|
| H A D | nvmem-cells.yaml | 4 $id: http://devicetree.org/schemas/mtd/partitions/nvmem-cells.yaml#
20 - $ref: /schemas/mtd/partitions/partition.yaml#
35 partitions {
36 compatible = "fixed-partitions";
68 partitions {
69 compatible = "fixed-partitions";
|
| /freebsd/contrib/llvm-project/lld/docs/ |
| H A D | Partitions.rst | 1 Partitions title
10 or a shared library) to be split into multiple pieces, or partitions. A
12 loadable partitions. The loadable partitions depend on the main partition
14 shared object, the main partition and the loadable partitions share a virtual
16 offset from the main partition. This allows the loadable partitions to refer
42 into partitions according to which sections of the program are reachable from
47 loadable partitions.
49 The following diagram illustrates how sections are assigned to partitions. Each
52 .. image:: partitions.svg
54 The result of linking a program that uses partitions is essentially an
[all …]
|
| /freebsd/stand/i386/gptboot/ |
| H A D | gptboot.8 | 59 The GPT standard allows a variable number of partitions, but
61 only boots from tables with 128 partitions or less.
64 checks and manages several attributes of GPT UFS partitions.
80 Multiple partitions may have the
88 attribute marks partitions that had the
128 attribute is set on any partitions, booting will be attempted from them
130 If no partitions with
139 partitions with only the
146 partitions.
151 attributes set on those partitions.
[all …]
|
| /freebsd/stand/efi/gptboot/ |
| H A D | gptboot.efi.8 | 44 Users with ZFS partitions should use
73 The GPT standard allows a variable number of partitions, but
75 only boots from tables with 128 partitions or less.
78 checks and manages several attributes of GPT UFS partitions.
97 Multiple partitions may have the
105 attribute marks partitions that had the
145 attribute is set on any partitions, booting will be attempted from them
147 If no partitions with
156 partitions with only the
163 partitions.
[all …]
|
| /freebsd/contrib/llvm-project/llvm/lib/Transforms/Scalar/ |
| H A D | LoopDistribute.cpp | 270 /// Holds the set of Partitions. It populates them, merges them and then
279 /// Returns the number of partitions.
295 // Initially we isolate memory instructions into as many partitions as
301 /// Merges adjacent non-cyclic partitions.
331 /// Merges the partitions according to various heuristics.
338 /// Merges partitions in order to ensure that no loads are duplicated.
344 /// Return if any partitions were merged.
352 // Step through the partitions and create equivalence between partitions in mergeToAvoidDuplicatedLoads()
353 // that contain the same load. Also put partitions in between them in the in mergeToAvoidDuplicatedLoads()
360 // If a load occurs in two partitions PartI and PartJ, merge all in mergeToAvoidDuplicatedLoads()
[all …]
|
| /freebsd/contrib/llvm-project/libcxx/src/pstl/ |
| H A D | libdispatch.cpp | 22 __chunk_partitions partitions; in __partition_chunks() local
23 partitions.__chunk_count_ = std::max<ptrdiff_t>(1, element_count / 256); in __partition_chunks()
24 partitions.__chunk_size_ = element_count / partitions.__chunk_count_; in __partition_chunks()
25 …partitions.__first_chunk_size_ = element_count - (partitions.__chunk_count_ - 1) * partitions.__ch… in __partition_chunks()
26 if (partitions.__chunk_count_ == 0 && element_count > 0) in __partition_chunks()
27 partitions.__chunk_count_ = 1; in __partition_chunks()
28 return partitions; in __partition_chunks()
|
| /freebsd/sys/contrib/device-tree/Bindings/mtd/ |
| H A D | partition.txt | 1 Flash partitions in device tree
12 To assist system software in locating partitions, we allow describing which
14 a subnode of the flash device that is named 'partitions'. It must have a
21 significant relation between partitions or some partition internally uses
24 Available bindings are listed in the "partitions" subdirectory.
27 Deprecated: partitions defined in flash node
30 For backwards compatibility partitions as direct subnodes of the flash device are
33 string are not considered partitions, as they may be used for other bindings.
|
| H A D | qcom,nandc.yaml | 62 qcom,boot-partitions:
71 partitions by defining first the offset and then the size.
128 qcom,boot-partitions: false
163 qcom,boot-partitions = <0x0 0x58a0000>;
165 partitions {
166 compatible = "fixed-partitions";
205 partitions {
206 compatible = "fixed-partitions";
|
| H A D | mtd.yaml | 32 partitions:
33 $ref: /schemas/mtd/partitions/partitions.yaml
40 $ref: partitions/partition.yaml
44 $ref: partitions/partition.yaml
|
| /freebsd/contrib/llvm-project/llvm/utils/TableGen/GlobalISel/ |
| H A D | GIMatchTree.cpp | |
| H A D | GIMatchTree.h | |
| /freebsd/stand/i386/gptzfsboot/ |
| H A D | gptzfsboot.8 | 41 The GPT standard allows a variable number of partitions, but
43 only boots from tables with 128 partitions or less.
47 hard disks or partitions on them.
50 supported partitions for all supported partition scheme types.
58 individual partitions are probed in their partition table order.
60 With the GPT scheme, only partitions of type
181 looks for ZFS meta-data only in MBR partitions
185 partitions that are traditionally called partitions.
|
| /freebsd/contrib/dialog/samples/install/ |
| H A D | setup.c | 29 /* max number of possible Linux/Swap/MsDos partitions */
68 /* We support to install from DOS/Linux-partitions. */
80 } partitions[MAX_PARTS]; variable
122 char *t = partitions[num_partition].name; in read_partitions()
135 partitions[num_partition].blocks = atoi(t); in read_partitions()
137 partitions[num_partition].type = Linux; in read_partitions()
141 partitions[num_partition].type = Swap; in read_partitions()
145 partitions[num_partition].type = MsDos; in read_partitions()
167 if (partitions[i].type == Linux) { in select_partition()
168 items[num * 2] = partitions[i].name; in select_partition()
[all …]
|
| /freebsd/usr.bin/mkimg/ |
| H A D | mkimg.1 | 78 utility does not treat it any differently from other partitions.
110 partitions and to round the size of the disk image.
123 option, but without specifying any partitions.
124 When the size required for all the partitions is larger than the
131 If the combined sizes of the given partitions exceed the size given with
174 No partitions are marked active when the value is 0.
197 output format, or for a detailed description of how to specify partitions,
372 To accommodate the need to have partitions named or numbered in a certain
375 utility allows for the specification of empty partitions.
393 utility supports assigning labels to the partitions specified.
|
| /freebsd/share/man/man4/ |
| H A D | hv_vmbus.4 | 43 guest and root partitions in Hyper-V.
54 The root partition then creates the child partitions which host
57 Child partitions do not have direct access to other hardware resources
67 child partitions.
68 Child partitions host Virtualization Service
|