9afb6540dc
to ensure the generated key is unique from each other since only
root pseduo file system really support st_ino field after:
commit d35fbf534d51f7ef72382d9666a1f19e07c6f00f
Author: Xiang Xiao <xiaoxiang@xiaomi.com>
Date: Fri Sep 16 14:24:55 2022 +0800
fs: Allocate unique serial number for the root pseduo file system node
Signed-off-by: Xiang Xiao <xiaoxiang@xiaomi.com>
77 lines
2.9 KiB
Plaintext
77 lines
2.9 KiB
Plaintext
#
|
|
# For a description of the syntax of this configuration file,
|
|
# see the file kconfig-language.txt in the NuttX tools repository.
|
|
#
|
|
|
|
comment "Non-standard Library Support"
|
|
|
|
config LIBC_CRC64_FAST
|
|
bool "Fast CRC64"
|
|
default n
|
|
---help---
|
|
Enable the CRC64 lookup table to compute the CRC64 faster.
|
|
|
|
config LIBC_KBDCODEC
|
|
bool "Keyboard CODEC"
|
|
default n
|
|
---help---
|
|
In NuttX, a keyboard/keypad driver is simply a character driver that
|
|
may have an (optional) encoding/decoding layer on the data returned
|
|
by the character driver. A keyboard may return simple text data
|
|
(alphabetic, numeric, and punctuation) or control characters
|
|
(enter, control-C, etc.). However, in addition, most keyboards
|
|
support actions that cannot be represented as text data. Such
|
|
actions include things like cursor controls (home, up arrow,
|
|
page down, etc.), editing functions (insert, delete, etc.), volume
|
|
controls, (mute, volume up, etc.) and other special functions.
|
|
Some special encoding may be required to multiplex these two classes
|
|
of data.
|
|
|
|
This option enables the functions that implement the encoding and
|
|
decoding of keyboard data. These are the interfaces prototyped in
|
|
include/nuttx/input/kbd_codec.h. While not correctly a part of
|
|
the C library, it is included here because the decoding side of this
|
|
interface must be accessible by end user programs.
|
|
|
|
config LIBC_SLCDCODEC
|
|
bool "Segment LCD CODEC"
|
|
default n
|
|
---help---
|
|
In NuttX, a character-oriented, segment LCD (SLCD) driver is simply
|
|
a character device that may have an (optional) encoding/decoding
|
|
layer on the data provided to the SLCD driver. The application may
|
|
provide simple text data (alphabetic, numeric, and punctuation) or
|
|
control characters (enter, control-C, etc.). However, in addition,
|
|
most SLCDs support actions that cannot be represented as text data.
|
|
Such actions include things like cursor controls (home, up arrow,
|
|
page down, etc.) and other special functions (e.g., blinking). Some
|
|
special encoding may be required to multiplex these two classes of
|
|
data.
|
|
|
|
This option enables the functions that implement the encoding and
|
|
decoding of SLCD data. These are the interfaces prototyped in
|
|
include/nuttx/lcd/slcd_codec.h. While not correctly a part of the C
|
|
library, it is included here because the encoding side of this
|
|
interface must be accessible by end user programs.
|
|
|
|
config LIBC_ENVPATH
|
|
bool "Support PATH Environment Variable"
|
|
default n
|
|
depends on !DISABLE_ENVIRON
|
|
---help---
|
|
Use the contents of the common environment variable to locate executable
|
|
or library files. Default: n
|
|
|
|
config LIBC_FTOK_VFS_PATH
|
|
string "Relative path to ftok storage"
|
|
default "/var/ftok"
|
|
---help---
|
|
The relative path to where ftok will exist in the root namespace.
|
|
|
|
config LIBC_MEM_FD_VFS_PATH
|
|
string "Relative path to memfd storage"
|
|
default "memfd"
|
|
depends on FS_TMPFS
|
|
---help---
|
|
The relative path to where memfd will exist in the tmpfs namespace.
|