Lines Matching +full:block +full:- +full:copy

33 # MTD block device support is select'ed if needed
39 	tristate "Caching block device access to MTD devices"
40 	depends on BLOCK
44 	  as block devices, it is possible to use MTD devices which are based
45 	  on RAM chips in this manner. This block device is a user of MTD
53 	  on flash chips to emulate a smaller block size. Needless to say,
61 	tristate "Readonly block device access to MTD devices"
62 	depends on MTD_BLOCK!=y && BLOCK
65 	  This allows you to mount read-only file systems (such as cramfs)
72 comment "Note that in some cases UBI block is preferred. See MTD_UBI_BLOCK."
77 	depends on BLOCK
81 	  is part of the PCMCIA specification. It uses a kind of pseudo-
82 	  file system on a flash device to emulate a block device with
83 	  512-byte sectors, on top of which you put a 'normal' file system.
87 	  legal - in the USA you are only permitted to use this on PCMCIA
89 	  permitted to copy, modify and distribute the code as you wish. Just
94 	depends on BLOCK
98 	  used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-
99 	  file system on a flash device to emulate a block device with
100 	  512-byte sectors, on top of which you put a 'normal' file system.
104 	  legal - in the USA you are only permitted to use this on DiskOnChip
106 	  permitted to copy, modify and distribute the code as you wish. Just
118 	depends on BLOCK
122 	  Layer which is used on M-Systems' newer DiskOnChip devices. It
123 	  uses a kind of pseudo-file system on a flash device to emulate
124 	  a block device with 512-byte sectors, on top of which you put
129 	  legal - in the USA you are only permitted to use this on DiskOnChip
131 	  permitted to copy, modify and distribute the code as you wish. Just
136 	depends on BLOCK
147 	depends on BLOCK
155 	depends on BLOCK
191 	  Provides volatile block device driver on top of mtd partition
219 source "drivers/mtd/spi-nor/Kconfig"