Home
last modified time | relevance | path

Searched full:gib (Results 1 – 25 of 246) sorted by relevance

12345678910

/kernel/linux/linux-5.10/drivers/mtd/nand/raw/
Dnand_ids.c126 EXTENDED_ID_NAND("NAND 1GiB 1,8V 8-bit", 0xA3, 1024, LP_OPTIONS),
127 EXTENDED_ID_NAND("NAND 1GiB 3,3V 8-bit", 0xD3, 1024, LP_OPTIONS),
128 EXTENDED_ID_NAND("NAND 1GiB 1,8V 16-bit", 0xB3, 1024, LP_OPTIONS16),
129 EXTENDED_ID_NAND("NAND 1GiB 3,3V 16-bit", 0xC3, 1024, LP_OPTIONS16),
132 EXTENDED_ID_NAND("NAND 2GiB 1,8V 8-bit", 0xA5, 2048, LP_OPTIONS),
133 EXTENDED_ID_NAND("NAND 2GiB 3,3V 8-bit", 0xD5, 2048, LP_OPTIONS),
134 EXTENDED_ID_NAND("NAND 2GiB 1,8V 16-bit", 0xB5, 2048, LP_OPTIONS16),
135 EXTENDED_ID_NAND("NAND 2GiB 3,3V 16-bit", 0xC5, 2048, LP_OPTIONS16),
138 EXTENDED_ID_NAND("NAND 4GiB 1,8V 8-bit", 0xA7, 4096, LP_OPTIONS),
139 EXTENDED_ID_NAND("NAND 4GiB 3,3V 8-bit", 0xD7, 4096, LP_OPTIONS),
[all …]
/kernel/linux/linux-6.6/drivers/mtd/nand/raw/
Dnand_ids.c136 EXTENDED_ID_NAND("NAND 1GiB 1,8V 8-bit", 0xA3, 1024, LP_OPTIONS),
137 EXTENDED_ID_NAND("NAND 1GiB 3,3V 8-bit", 0xD3, 1024, LP_OPTIONS),
138 EXTENDED_ID_NAND("NAND 1GiB 1,8V 16-bit", 0xB3, 1024, LP_OPTIONS16),
139 EXTENDED_ID_NAND("NAND 1GiB 3,3V 16-bit", 0xC3, 1024, LP_OPTIONS16),
142 EXTENDED_ID_NAND("NAND 2GiB 1,8V 8-bit", 0xA5, 2048, LP_OPTIONS),
143 EXTENDED_ID_NAND("NAND 2GiB 3,3V 8-bit", 0xD5, 2048, LP_OPTIONS),
144 EXTENDED_ID_NAND("NAND 2GiB 1,8V 16-bit", 0xB5, 2048, LP_OPTIONS16),
145 EXTENDED_ID_NAND("NAND 2GiB 3,3V 16-bit", 0xC5, 2048, LP_OPTIONS16),
148 EXTENDED_ID_NAND("NAND 4GiB 1,8V 8-bit", 0xA7, 4096, LP_OPTIONS),
149 EXTENDED_ID_NAND("NAND 4GiB 3,3V 8-bit", 0xD7, 4096, LP_OPTIONS),
[all …]
/kernel/linux/linux-6.6/arch/x86/include/asm/
Dpage_64_types.h86 * This can be at most 1 GiB, due to the fixmap living in the next 1 GiB (see
89 * On KASLR use 1 GiB by default, leaving 1 GiB for modules once the
92 * If KASLR is disabled we can shrink it to 0.5 GiB and increase the size
93 * of the modules area to 1.5 GiB.
/kernel/linux/linux-5.10/arch/x86/include/asm/
Dpage_64_types.h101 * Maximum kernel image size is limited to 1 GiB, due to the fixmap living
102 * in the next 1 GiB (see level2_kernel_pgt in arch/x86/kernel/head_64.S).
104 * On KASLR use 1 GiB by default, leaving 1 GiB for modules once the
107 * If KASLR is disabled we can shrink it to 0.5 GiB and increase the size
108 * of the modules area to 1.5 GiB.
/kernel/linux/linux-6.6/Documentation/filesystems/ext4/
Dblocks.rst57 - 32GiB
74 - 16GiB
75 - 256GiB
119 - 32GiB
136 - 16GiB
137 - 256GiB
/kernel/linux/linux-5.10/Documentation/filesystems/ext4/
Dblocks.rst57 - 32GiB
74 - 16GiB
75 - 256GiB
119 - 32GiB
136 - 16GiB
137 - 256GiB
/kernel/linux/linux-5.10/Documentation/vm/
Dhighmem.rst26 kernel entry/exit. This means the available virtual memory space (4GiB on
29 The traditional split for architectures using this approach is 3:1, 3GiB for
30 userspace and the top 1GiB for kernel space::
40 This means that the kernel can at most map 1GiB of physical memory at any one
128 The i386 arch, under some circumstances, will permit you to stick up to 64GiB
144 The general recommendation is that you don't use more than 8GiB on a 32-bit
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/mtd/
Dpartition.txt48 size/address (aka the value is below 4 GiB)
50 size/address (aka the value is 4 GiB or greater).
95 /* a 4 GiB partition */
109 /* an 8 GiB partition */
115 /* a 4 GiB partition */
/kernel/linux/linux-6.6/Documentation/mm/
Dhighmem.rst24 kernel entry/exit. This means the available virtual memory space (4GiB on
27 The traditional split for architectures using this approach is 3:1, 3GiB for
28 userspace and the top 1GiB for kernel space::
38 This means that the kernel can at most map 1GiB of physical memory at any one
186 The i386 arch, under some circumstances, will permit you to stick up to 64GiB
202 The general recommendation is that you don't use more than 8GiB on a 32-bit
/kernel/linux/linux-5.10/arch/arm64/boot/dts/realtek/
Drtd1395-bpi-m4.dts16 reg = <0x2f000 0x3ffd1000>; /* boot ROM to 1 GiB or 2 GiB */
Drtd1295-xnano-x5.dts16 reg = <0x1f000 0x3ffe1000>; /* boot ROM to 1 GiB or 2 GiB */
Drtd1395-lionskin.dts16 reg = <0x2f000 0x3ffd1000>; /* boot ROM to 1 GiB or 2 GiB */
/kernel/linux/linux-6.6/arch/arm64/boot/dts/realtek/
Drtd1295-xnano-x5.dts16 reg = <0x1f000 0x3ffe1000>; /* boot ROM to 1 GiB or 2 GiB */
Drtd1395-bpi-m4.dts16 reg = <0x2f000 0x3ffd1000>; /* boot ROM to 1 GiB or 2 GiB */
Drtd1395-lionskin.dts16 reg = <0x2f000 0x3ffd1000>; /* boot ROM to 1 GiB or 2 GiB */
/kernel/linux/linux-6.6/arch/arm64/boot/dts/amlogic/
Dmeson-axg-jethome-jethub-j110-rev-3.dts16 /* 2GiB or 4GiB RAM */
Dmeson-gxl-s905w-tx3-mini.dts20 reg = <0x0 0x0 0x0 0x40000000>; /* 1 GiB or 2 GiB */
Dmeson-axg-jethome-jethub-j110-rev-2.dts16 /* 2GiB or 4GiB RAM */
Dmeson-gxm-wetek-core2.dts19 reg = <0x0 0x0 0x0 0x80000000>; /* 2 GiB or 3 GiB */
/kernel/linux/linux-5.10/arch/arm64/boot/dts/amlogic/
Dmeson-gxl-s905w-tx3-mini.dts20 reg = <0x0 0x0 0x0 0x40000000>; /* 1 GiB or 2 GiB */
Dmeson-gxm-wetek-core2.dts19 reg = <0x0 0x0 0x0 0x80000000>; /* 2 GiB or 3 GiB */
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/mtd/partitions/
Dfixed-partitions.yaml76 /* a 4 GiB partition */
90 /* an 8 GiB partition */
96 /* a 4 GiB partition */
/kernel/linux/linux-5.10/arch/riscv/
DKconfig240 # such that it can only map 2GiB of memory.
264 bool "1GiB"
267 bool "2GiB"
270 bool "128GiB"
/kernel/linux/linux-6.6/arch/arm64/boot/dts/exynos/
Dexynos850-e850-96.dts33 * RAM: 4 GiB (eMCP):
34 * - 2 GiB at 0x80000000
35 * - 2 GiB at 0x880000000
/kernel/linux/linux-6.6/tools/perf/Documentation/
Dperf-iostat.txt57 375083606016 bytes (375 GB, 349 GiB) copied, 215.974 s, 1.7 GB/s
76 375083606016 bytes (375 GB, 349 GiB) copied, 197.08 s, 1.9 GB/s

12345678910