blob: cd8533e68fd7b8ed21c555f3bdac4f9dc9e41bdb (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
|
#
# For a description of the syntax of this configuration file,
# see misc/tools/kconfig-language.txt.
#
config EXAMPLES_MTDPART
bool "MTD partition test"
default n
depends on MTD_PARTITION && !BUILD_PROTECTED && !BUILD_KERNEL
---help---
Enable the MTD partition test example.
NOTE: This example uses some internal NuttX interfaces and, hence,
is not available in the kernel build.
if EXAMPLES_MTDPART
config EXAMPLES_MTDPART_ARCHINIT
bool "Architecture-specific initialization"
default n
---help---
The default is to use the RAM MTD device at drivers/mtd/rammtd.c.
But an architecture-specific MTD driver can be used instead by
defining EXAMPLES_MTDPART_ARCHINIT. In this case, the
initialization logic will call mtdpart_archinitialize() to obtain
the MTD driver instance.
config EXAMPLES_MTDPART_NEBLOCKS
int "Number of erase blocks (simulated)"
default 32
depends on !EXAMPLES_MTDPART_ARCHINIT
---help---
When EXAMPLES_MTDPART_ARCHINIT is not defined, this test will use
the RAM MTD device at drivers/mtd/rammtd.c to simulate FLASH. In
this case, this value must be provided to give the nubmer of erase
blocks in MTD RAM device.
The size of the allocated RAM drive will be:
EXAMPLES_MTDPART_ERASESIZE * EXAMPLES_MTDPART_NEBLOCKS
config EXAMPLES_MTDPART_NPARTITIONS
int "Number of partitions"
default 3
---help---
This setting provides the number of partitions to test. The
test will divide the reported size of the MTD device into equal-
sized sub-regions for each test partition.
endif
|
