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