# SPDX-License-Identifier: GPL-2.0-only # # MemoryStick core configuration # comment "MemoryStick drivers" config [31mCONFIG_MEMSTICK_UNSAFE_RESUME[0m 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 [31mCONFIG_MSPRO_BLOCK[0m tristate "MemoryStick Pro block device driver" depends on [31mCONFIG_BLOCK[0m 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 [31mCONFIG_M[0m here. config [31mCONFIG_MS_BLOCK[0m tristate "MemoryStick Standard device driver" depends on [31mCONFIG_BLOCK[0m help Say Y here to enable the MemoryStick Standard device driver support. This provides a block device driver, which you can use to mount the filesystem. This driver works with old (bulky) MemoryStick and MemoryStick Duo but not PRO. Say Y if you have such card. Driver is new and not yet well tested, thus it can damage your card (even permanently) |