diff options
author | Thomas Gleixner <tglx@linutronix.de> | 2005-11-07 06:15:26 -0500 |
---|---|---|
committer | Thomas Gleixner <tglx@mtd.linutronix.de> | 2005-11-07 07:37:38 -0500 |
commit | 97894cda5773e59bd13e87b72077751099419a9f (patch) | |
tree | 9a039ab8c122ae9a4f64d285e2da0efd1356789e /drivers/mtd/Kconfig | |
parent | b95f9609c761a14d1e7be1a89f2a66399b5ae343 (diff) |
[MTD] core: Clean up trailing white spaces
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'drivers/mtd/Kconfig')
-rw-r--r-- | drivers/mtd/Kconfig | 32 |
1 files changed, 16 insertions, 16 deletions
diff --git a/drivers/mtd/Kconfig b/drivers/mtd/Kconfig index 3dbfbafb3481..f6b775e63ac8 100644 --- a/drivers/mtd/Kconfig +++ b/drivers/mtd/Kconfig | |||
@@ -1,4 +1,4 @@ | |||
1 | # $Id: Kconfig,v 1.10 2005/07/11 10:39:27 gleixner Exp $ | 1 | # $Id: Kconfig,v 1.11 2005/11/07 11:14:19 gleixner Exp $ |
2 | 2 | ||
3 | menu "Memory Technology Devices (MTD)" | 3 | menu "Memory Technology Devices (MTD)" |
4 | 4 | ||
@@ -10,7 +10,7 @@ config MTD | |||
10 | will provide the generic support for MTD drivers to register | 10 | will provide the generic support for MTD drivers to register |
11 | themselves with the kernel and for potential users of MTD devices | 11 | themselves with the kernel and for potential users of MTD devices |
12 | to enumerate the devices which are present and obtain a handle on | 12 | to enumerate the devices which are present and obtain a handle on |
13 | them. It will also allow you to select individual drivers for | 13 | them. It will also allow you to select individual drivers for |
14 | particular hardware and users of MTD devices. If unsure, say N. | 14 | particular hardware and users of MTD devices. If unsure, say N. |
15 | 15 | ||
16 | config MTD_DEBUG | 16 | config MTD_DEBUG |
@@ -61,11 +61,11 @@ config MTD_REDBOOT_PARTS | |||
61 | 61 | ||
62 | If you need code which can detect and parse this table, and register | 62 | If you need code which can detect and parse this table, and register |
63 | MTD 'partitions' corresponding to each image in the table, enable | 63 | MTD 'partitions' corresponding to each image in the table, enable |
64 | this option. | 64 | this option. |
65 | 65 | ||
66 | You will still need the parsing functions to be called by the driver | 66 | You will still need the parsing functions to be called by the driver |
67 | for your particular device. It won't happen automatically. The | 67 | for your particular device. It won't happen automatically. The |
68 | SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for | 68 | SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for |
69 | example. | 69 | example. |
70 | 70 | ||
71 | config MTD_REDBOOT_DIRECTORY_BLOCK | 71 | config MTD_REDBOOT_DIRECTORY_BLOCK |
@@ -81,10 +81,10 @@ config MTD_REDBOOT_DIRECTORY_BLOCK | |||
81 | partition table. A zero or positive value gives an absolete | 81 | partition table. A zero or positive value gives an absolete |
82 | erase block number. A negative value specifies a number of | 82 | erase block number. A negative value specifies a number of |
83 | sectors before the end of the device. | 83 | sectors before the end of the device. |
84 | 84 | ||
85 | For example "2" means block number 2, "-1" means the last | 85 | For example "2" means block number 2, "-1" means the last |
86 | block and "-2" means the penultimate block. | 86 | block and "-2" means the penultimate block. |
87 | 87 | ||
88 | config MTD_REDBOOT_PARTS_UNALLOCATED | 88 | config MTD_REDBOOT_PARTS_UNALLOCATED |
89 | bool " Include unallocated flash regions" | 89 | bool " Include unallocated flash regions" |
90 | depends on MTD_REDBOOT_PARTS | 90 | depends on MTD_REDBOOT_PARTS |
@@ -105,11 +105,11 @@ config MTD_CMDLINE_PARTS | |||
105 | ---help--- | 105 | ---help--- |
106 | Allow generic configuration of the MTD paritition tables via the kernel | 106 | Allow generic configuration of the MTD paritition tables via the kernel |
107 | command line. Multiple flash resources are supported for hardware where | 107 | command line. Multiple flash resources are supported for hardware where |
108 | different kinds of flash memory are available. | 108 | different kinds of flash memory are available. |
109 | 109 | ||
110 | You will still need the parsing functions to be called by the driver | 110 | You will still need the parsing functions to be called by the driver |
111 | for your particular device. It won't happen automatically. The | 111 | for your particular device. It won't happen automatically. The |
112 | SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for | 112 | SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for |
113 | example. | 113 | example. |
114 | 114 | ||
115 | The format for the command line is as follows: | 115 | The format for the command line is as follows: |
@@ -118,12 +118,12 @@ config MTD_CMDLINE_PARTS | |||
118 | <mtddef> := <mtd-id>:<partdef>[,<partdef>] | 118 | <mtddef> := <mtd-id>:<partdef>[,<partdef>] |
119 | <partdef> := <size>[@offset][<name>][ro] | 119 | <partdef> := <size>[@offset][<name>][ro] |
120 | <mtd-id> := unique id used in mapping driver/device | 120 | <mtd-id> := unique id used in mapping driver/device |
121 | <size> := standard linux memsize OR "-" to denote all | 121 | <size> := standard linux memsize OR "-" to denote all |
122 | remaining space | 122 | remaining space |
123 | <name> := (NAME) | 123 | <name> := (NAME) |
124 | 124 | ||
125 | Due to the way Linux handles the command line, no spaces are | 125 | Due to the way Linux handles the command line, no spaces are |
126 | allowed in the partition definition, including mtd id's and partition | 126 | allowed in the partition definition, including mtd id's and partition |
127 | names. | 127 | names. |
128 | 128 | ||
129 | Examples: | 129 | Examples: |
@@ -240,7 +240,7 @@ config INFTL | |||
240 | tristate "INFTL (Inverse NAND Flash Translation Layer) support" | 240 | tristate "INFTL (Inverse NAND Flash Translation Layer) support" |
241 | depends on MTD | 241 | depends on MTD |
242 | ---help--- | 242 | ---help--- |
243 | This provides support for the Inverse NAND Flash Translation | 243 | This provides support for the Inverse NAND Flash Translation |
244 | Layer which is used on M-Systems' newer DiskOnChip devices. It | 244 | Layer which is used on M-Systems' newer DiskOnChip devices. It |
245 | uses a kind of pseudo-file system on a flash device to emulate | 245 | uses a kind of pseudo-file system on a flash device to emulate |
246 | a block device with 512-byte sectors, on top of which you put | 246 | a block device with 512-byte sectors, on top of which you put |
@@ -257,8 +257,8 @@ config RFD_FTL | |||
257 | tristate "Resident Flash Disk (Flash Translation Layer) support" | 257 | tristate "Resident Flash Disk (Flash Translation Layer) support" |
258 | depends on MTD | 258 | depends on MTD |
259 | ---help--- | 259 | ---help--- |
260 | This provides support for the flash translation layer known | 260 | This provides support for the flash translation layer known |
261 | as the Resident Flash Disk (RFD), as used by the Embedded BIOS | 261 | as the Resident Flash Disk (RFD), as used by the Embedded BIOS |
262 | of General Software. There is a blurb at: | 262 | of General Software. There is a blurb at: |
263 | 263 | ||
264 | http://www.gensw.com/pages/prod/bios/rfd.htm | 264 | http://www.gensw.com/pages/prod/bios/rfd.htm |