You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
27 lines
947 B
27 lines
947 B
17 years ago
|
#
|
||
|
|
# MemoryStick core configuration
|
||
|
|
#
|
||
|
|
|
||
|
|
comment "MemoryStick drivers"
|
||
|
|
|
||
|
|
config MEMSTICK_UNSAFE_RESUME
|
||
|
|
bool "Allow unsafe resume (DANGEROUS)"
|
||
|
|
help
|
||
|
|
If you say Y here, the MemoryStick layer will assume that all
|
||
|
|
cards stayed in their respective slots during the suspend. The
|
||
|
|
normal behaviour is to remove them at suspend and
|
||
|
|
redetecting them at resume. Breaking this assumption will
|
||
|
|
in most cases result in data corruption.
|
||
|
|
|
||
|
|
This option is usually just for embedded systems which use
|
||
|
|
a MemoryStick card for rootfs. Most people should say N here.
|
||
|
|
|
||
|
|
config MSPRO_BLOCK
|
||
|
|
tristate "MemoryStick Pro block device driver"
|
||
|
|
depends on BLOCK
|
||
|
|
help
|
||
|
|
Say Y here to enable the MemoryStick Pro block device driver
|
||
|
|
support. This provides a block device driver, which you can use
|
||
|
|
to mount the filesystem. Almost everyone wishing MemoryStick
|
||
|
|
support should say Y or M here.
|