summaryrefslogtreecommitdiff
path: root/nuttx/fs/nxffs/Kconfig
blob: f6aede4a21a357e4d4567175e8cfcc2230c61d88 (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
51
52
53
54
55
#
# For a description of the syntax of this configuration file,
# see misc/tools/kconfig-language.txt.
#

menu "NXFFS file system configuration"
comment "NXFFS file system configuration"

config FS_NXFFS
	bool "NXFFS file system"
	default n
	depends on !DISABLE_MOUNTPOINT
	---help---
		Enable NuttX FLASH file system (NXFF) support.

if FS_NXFFS
config NXFFS_ERASEDSTATE
	bool "FLASH erased state"
	default n
	---help---	
		The erased state of FLASH. 
		This must have one of the values of 0xff or 0x00.
		Default: 0xff.

config NXFFS_PACKTHRESHOLD
	bool "Re-packing threshold"
	default n
	---help---
		When packing flash file data,
		don't both with file chunks smaller than this number of data bytes.
		Default: 32.

config NXFFS_MAXNAMLEN
	bool "Maximum file name length"
	default n
	---help---	
		The maximum size of an NXFFS file name.
		Default: 255.

config NXFFS_TAILTHRESHOLD
	bool "Tail threshold"
	default n
	---help---	
		clean-up can either mean
		packing files together toward the end of the file or, if file are
		deleted at the end of the file, clean up can simply mean erasing
		the end of FLASH memory so that it can be re-used again.  However,
		doing this can also harm the life of the FLASH part because it can
		mean that the tail end of the FLASH is re-used too often. This
		threshold determines if/when it is worth erased the tail end of FLASH
		and making it available for re-use (and possible over-wear).
		Default: 8192.

endif
endmenu