1baf8532aSAlex Dubov# 2baf8532aSAlex Dubov# MemoryStick core configuration 3baf8532aSAlex Dubov# 4baf8532aSAlex Dubov 5baf8532aSAlex Dubovcomment "MemoryStick drivers" 6baf8532aSAlex Dubov 7baf8532aSAlex Dubovconfig MEMSTICK_UNSAFE_RESUME 8baf8532aSAlex Dubov bool "Allow unsafe resume (DANGEROUS)" 9baf8532aSAlex Dubov help 10baf8532aSAlex Dubov If you say Y here, the MemoryStick layer will assume that all 11baf8532aSAlex Dubov cards stayed in their respective slots during the suspend. The 12baf8532aSAlex Dubov normal behaviour is to remove them at suspend and 13baf8532aSAlex Dubov redetecting them at resume. Breaking this assumption will 14baf8532aSAlex Dubov in most cases result in data corruption. 15baf8532aSAlex Dubov 16baf8532aSAlex Dubov This option is usually just for embedded systems which use 17baf8532aSAlex Dubov a MemoryStick card for rootfs. Most people should say N here. 18baf8532aSAlex Dubov 19baf8532aSAlex Dubovconfig MSPRO_BLOCK 20baf8532aSAlex Dubov tristate "MemoryStick Pro block device driver" 21baf8532aSAlex Dubov depends on BLOCK 22baf8532aSAlex Dubov help 23baf8532aSAlex Dubov Say Y here to enable the MemoryStick Pro block device driver 24baf8532aSAlex Dubov support. This provides a block device driver, which you can use 25baf8532aSAlex Dubov to mount the filesystem. Almost everyone wishing MemoryStick 26baf8532aSAlex Dubov support should say Y or M here. 27