nuttx-apps/examples/mtdpart/Kconfig
anchao 220653f21c Squashed commit of the following:
Author: anchao <anchao@pinecone.net>

     apps/, most main() function: Correct CONFIG_BUILD_LOADABLE usage
     Loadable apps/: Correct loadable symbol table generate
     apps/system/ubloxmodem:  Fix build break
     apps/examples/ostest: start restart/waitpid/user test from main loop
     apps/nshlib:  Expand reboot and poweroff commands to include a second, optional mode argument

    Author: Gregory Nutt <gnutt@nuttx.org>

     An attempt to fix build issues.  Does not work.
     apps/examples/ostest:  Fix some inappropriate renaming of static functions introduced with recent patches.
     apps/builtin/exec_builtin.c:  Fix a error introduced by recent comments.  Found in build testing.

    Author: anchao <anchao@pinecone.net>

     apps/builtin/exec_builtin.c:  Try posix_spawn if builtin apps do not have have an entry point.
     apps/Application.mk: introduce MODULE config to simplify tristate(m)
     apps/nsh:  Change the nuttx shell module type to tristate
     apps:  Add loadable application support
     script/mksymtab:  Generate symbol table name by default
     apps/builtin:  Allow loadable applications can register with apps/builtin.
2018-08-23 11:06:15 -06:00

51 lines
1.5 KiB
Plaintext

#
# For a description of the syntax of this configuration file,
# see the file kconfig-language.txt in the NuttX tools repository.
#
config EXAMPLES_MTDPART
bool "MTD partition test"
default n
depends on MTD_PARTITION && !BUILD_PROTECTED && !BUILD_LOADABLE
---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