A little bit of file system configuration logic

git-svn-id: https://nuttx.svn.sourceforge.net/svnroot/nuttx/trunk@4586 7fd9a85b-ad96-42d3-883c-3090e2eb8679
This commit is contained in:
patacongo 2012-04-10 23:01:40 +00:00
parent 52ff9424e1
commit 77dda92fc9
6 changed files with 124 additions and 0 deletions

View File

@ -2,3 +2,10 @@
# For a description of the syntax of this configuration file, # For a description of the syntax of this configuration file,
# see misc/tools/kconfig-language.txt. # see misc/tools/kconfig-language.txt.
# #
comment "File system configuration"
source fs/fat/Kconfig
source fs/mmap/Kconfig
source fs/nfs/Kconfig
source fs/nxffs/Kconfig
source fs/romfs/Kconfig

View File

@ -2,3 +2,62 @@
# For a description of the syntax of this configuration file, # For a description of the syntax of this configuration file,
# see misc/tools/kconfig-language.txt. # see misc/tools/kconfig-language.txt.
# #
menu "FAT file system configuration"
comment "FAT file system configuration"
config FS_FAT
bool "FAT file system"
default n
# depends on CONFIG_NFILE_DESCRIPTORS > 0 && !CONFIG_DISABLE_MOUNTPOINT
---help---
Enable FAT filesystem support
config FAT_SECTORSIZE
int "FAT sector size"
default 512
depends on FS_FAT
---help---
Max supported sector size
config FAT_LCNAMES
bool "FAT upper/lower names"
default n
depends on FS_FAT
---help---
Enable use of the NT-style upper/lower case 8.3
file name support.
config FAT_LFN
bool "FAT long file names"
default n
depends on FS_FAT
---help---
Enable FAT long file names. NOTE: Microsoft claims
patents on FAT long file name technology. Please read the
disclaimer in the top-level COPYING file and only enable this
feature if you understand these issues.
config FAT_MAXFNAME
int "FAT maximum file name size"
default n
depends on FAT_LFN
---help---
If CONFIG_FAT_LFN is defined, then the
default, maximum long file name is 255 bytes. This can eat up
a lot of memory (especially stack space). If you are willing
to live with some non-standard, short long file names, then
define this value. A good choice would be the same value as
selected for CONFIG_NAME_MAX which will limit the visibility
of longer file names anyway.
config FS_FATTIME
bool "FAT timestamps"
default n
depends on FS_FAT
---help---
Support FAT date and time. NOTE: There is not
much sense in supporting FAT date and time unless you have a
hardware RTC or other way to get the time and date.
endmenu

View File

@ -2,3 +2,5 @@
# For a description of the syntax of this configuration file, # For a description of the syntax of this configuration file,
# see misc/tools/kconfig-language.txt. # see misc/tools/kconfig-language.txt.
# #
comment "File mapping emulation"

View File

@ -2,3 +2,5 @@
# For a description of the syntax of this configuration file, # For a description of the syntax of this configuration file,
# see misc/tools/kconfig-language.txt. # see misc/tools/kconfig-language.txt.
# #
comment "Network file system (NFS) client file system"

View File

@ -2,3 +2,55 @@
# For a description of the syntax of this configuration file, # For a description of the syntax of this configuration file,
# see misc/tools/kconfig-language.txt. # 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
---help---
Enable NuttX FLASH file system (NXFF) support.
config NXFFS_ERASEDSTATE
bool "FLASH erased state"
default n
depends on FS_NXFFS
---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
depends on FS_NXFFS
---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
depends on FS_NXFFS
---help---
The maximum size of an NXFFS file name.
Default: 255.
config NXFFS_TAILTHRESHOLD
bool "Tail threshold"
default n
depends on FS_NXFFS
---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.
endmenu

View File

@ -2,3 +2,5 @@
# For a description of the syntax of this configuration file, # For a description of the syntax of this configuration file,
# see misc/tools/kconfig-language.txt. # see misc/tools/kconfig-language.txt.
# #
comment "ROMFS file system"