Lines Matching refs:of

8 	  themselves with the kernel and for potential users of MTD devices
11 	  particular hardware and users of MTD devices. If unsure, say N.
26 	  Determines the verbosity level of the MTD debugging messages.
40 	  into multiple 'partitions', each of which appears to the user as
46 	  'normal' form of partitioning used on a block device.
61 	  'images' in flash devices by putting a table one of the erase
63 	  the offsets, lengths and names of all the images stored in the
76 	int "Location of RedBoot partition table"
86 	  erase block number. A negative value specifies a number of
87 	  sectors before the end of the device.
110 	  Allow generic configuration of the MTD partition tables via the kernel
112 	  different kinds of flash memory are available.
164 	  the partition map from the children of the flash node,
165 	  as described in Documentation/powerpc/booting-without-of.txt.
181 	  the device, or to erase parts of it.
200 	  on RAM chips in this manner. This block device is a user of MTD
205 	  (although JFFS and JFFS2 don't actually use any of the functionality
206 	  of the mtdblock device).
222 	  from an MTD device, without the overhead (and danger) of the caching
234 	  is part of the PCMCIA specification. It uses a kind of pseudo-
236 	  512-byte sectors, on top of which you put a 'normal' file system.
241 	  hardware, although under the terms of the GPL you're obviously
251 	  used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-
253 	  512-byte sectors, on top of which you put a 'normal' file system.
258 	  hardware, although under the terms of the GPL you're obviously
276 	  uses a kind of pseudo-file system on a flash device to emulate
277 	  a block device with 512-byte sectors, on top of which you put
283 	  hardware, although under the terms of the GPL you're obviously
294 	  of General Software. There is a blurb at: