2012-04-06 18:33:17 +02:00
|
|
|
#
|
|
|
|
|
# For a description of the syntax of this configuration file,
|
2015-06-28 16:14:53 +02:00
|
|
|
# see the file kconfig-language.txt in the NuttX tools repository.
|
2012-04-06 18:33:17 +02:00
|
|
|
#
|
2012-04-13 04:14:09 +02:00
|
|
|
|
2019-01-24 21:44:54 +01:00
|
|
|
config TESTING_NXFFS
|
2018-09-03 17:29:56 +02:00
|
|
|
tristate "NXFFS file system example"
|
2012-04-13 04:14:09 +02:00
|
|
|
default n
|
|
|
|
|
---help---
|
|
|
|
|
Enable the NXFFS file system example
|
|
|
|
|
|
2019-01-24 21:44:54 +01:00
|
|
|
if TESTING_NXFFS
|
2013-04-30 23:54:02 +02:00
|
|
|
|
2019-01-24 21:44:54 +01:00
|
|
|
config TESTING_NXFFS_ARCHINIT
|
2013-04-30 23:54:02 +02:00
|
|
|
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
|
2019-01-24 21:44:54 +01:00
|
|
|
defining TESTING_NXFFS_ARCHINIT. In this case, the
|
2013-04-30 23:54:02 +02:00
|
|
|
initialization logic will call mtdpart_archinitialize() to obtain
|
|
|
|
|
the MTD driver instance.
|
|
|
|
|
|
2019-01-24 21:44:54 +01:00
|
|
|
config TESTING_NXFFS_NEBLOCKS
|
2013-04-30 23:54:02 +02:00
|
|
|
int "Number of erase blocks (simulated)"
|
|
|
|
|
default 32
|
2019-01-24 21:44:54 +01:00
|
|
|
depends on !TESTING_NXFFS_ARCHINIT
|
2013-04-30 23:54:02 +02:00
|
|
|
---help---
|
2019-01-24 21:44:54 +01:00
|
|
|
When TESTING_NXFFS_ARCHINIT is not defined, this test will use
|
2013-04-30 23:54:02 +02:00
|
|
|
the RAM MTD device at drivers/mtd/rammtd.c to simulate FLASH. In
|
2020-02-23 05:51:44 +01:00
|
|
|
this case, this value must be provided to give the number of erase
|
2013-04-30 23:54:02 +02:00
|
|
|
blocks in MTD RAM device.
|
|
|
|
|
|
|
|
|
|
The size of the allocated RAM drive will be:
|
|
|
|
|
|
2019-01-24 21:44:54 +01:00
|
|
|
RAMMTD_ERASESIZE * TESTING_NXFFS_NEBLOCKS
|
2013-04-30 23:54:02 +02:00
|
|
|
|
2019-01-24 21:44:54 +01:00
|
|
|
config TESTING_NXFFS_MAXNAME
|
2013-04-30 23:54:02 +02:00
|
|
|
int "Max name size"
|
|
|
|
|
default 128
|
|
|
|
|
range 1 255
|
|
|
|
|
---help---
|
|
|
|
|
Determines the maximum size of names used in the filesystem
|
|
|
|
|
|
2023-06-20 16:05:49 +02:00
|
|
|
config TESTING_NXFFS_MAXFILE
|
2013-04-30 23:54:02 +02:00
|
|
|
int "Max file size"
|
|
|
|
|
default 8192
|
|
|
|
|
---help---
|
|
|
|
|
Determines the maximum size of a file
|
|
|
|
|
|
2019-01-24 21:44:54 +01:00
|
|
|
config TESTING_NXFFS_MAXIO
|
2013-04-30 23:54:02 +02:00
|
|
|
int "Max I/O"
|
|
|
|
|
default 347
|
|
|
|
|
|
2019-01-24 21:44:54 +01:00
|
|
|
config TESTING_NXFFS_MAXOPEN
|
2013-04-30 23:54:02 +02:00
|
|
|
int "Max open files"
|
|
|
|
|
default 512
|
|
|
|
|
|
2019-01-24 21:44:54 +01:00
|
|
|
config TESTING_NXFFS_MOUNTPT
|
2013-04-30 23:54:02 +02:00
|
|
|
string "NXFFS mountpoint"
|
|
|
|
|
default "/mnt/nxffs"
|
|
|
|
|
|
2019-01-24 21:44:54 +01:00
|
|
|
config TESTING_NXFFS_NLOOPS
|
2013-04-30 23:54:02 +02:00
|
|
|
int "Number of test loops"
|
|
|
|
|
default 100
|
|
|
|
|
|
2019-01-24 21:44:54 +01:00
|
|
|
config TESTING_NXFFS_VERBOSE
|
2013-04-30 23:54:02 +02:00
|
|
|
bool "Verbose output"
|
|
|
|
|
default n
|
|
|
|
|
|
2023-06-20 16:05:49 +02:00
|
|
|
endif # TESTING_NXFFS
|
