2007-04-19 15:21:41 -06:00
|
|
|
menuconfig MTD
|
2005-04-16 16:20:36 -06:00
|
|
|
tristate "Memory Technology Device (MTD) support"
|
2012-02-06 17:22:50 -07:00
|
|
|
depends on GENERIC_IO
|
2005-04-16 16:20:36 -06:00
|
|
|
help
|
|
|
|
Memory Technology Devices are flash, RAM and similar chips, often
|
|
|
|
used for solid state file systems on embedded devices. This option
|
|
|
|
will provide the generic support for MTD drivers to register
|
|
|
|
themselves with the kernel and for potential users of MTD devices
|
|
|
|
to enumerate the devices which are present and obtain a handle on
|
2005-11-07 04:15:26 -07:00
|
|
|
them. It will also allow you to select individual drivers for
|
2005-04-16 16:20:36 -06:00
|
|
|
particular hardware and users of MTD devices. If unsure, say N.
|
|
|
|
|
2007-04-19 15:21:41 -06:00
|
|
|
if MTD
|
|
|
|
|
2009-06-13 04:15:18 -06:00
|
|
|
config MTD_TESTS
|
2011-10-30 10:28:49 -06:00
|
|
|
tristate "MTD tests support (DANGEROUS)"
|
2009-06-13 04:15:18 -06:00
|
|
|
depends on m
|
|
|
|
help
|
|
|
|
This option includes various MTD tests into compilation. The tests
|
|
|
|
should normally be compiled as kernel modules. The modules perform
|
|
|
|
various checks and verifications when loaded.
|
|
|
|
|
2011-10-30 10:28:49 -06:00
|
|
|
WARNING: some of the tests will ERASE entire MTD device which they
|
|
|
|
test. Do not use these tests unless you really know what you do.
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
config MTD_REDBOOT_PARTS
|
|
|
|
tristate "RedBoot partition table parsing"
|
|
|
|
---help---
|
|
|
|
RedBoot is a ROM monitor and bootloader which deals with multiple
|
|
|
|
'images' in flash devices by putting a table one of the erase
|
|
|
|
blocks on the device, similar to a partition table, which gives
|
|
|
|
the offsets, lengths and names of all the images stored in the
|
|
|
|
flash.
|
|
|
|
|
|
|
|
If you need code which can detect and parse this table, and register
|
|
|
|
MTD 'partitions' corresponding to each image in the table, enable
|
2005-11-07 04:15:26 -07:00
|
|
|
this option.
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
You will still need the parsing functions to be called by the driver
|
2005-11-07 04:15:26 -07:00
|
|
|
for your particular device. It won't happen automatically. The
|
|
|
|
SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for
|
2005-04-16 16:20:36 -06:00
|
|
|
example.
|
|
|
|
|
2010-10-30 00:35:02 -06:00
|
|
|
if MTD_REDBOOT_PARTS
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
config MTD_REDBOOT_DIRECTORY_BLOCK
|
|
|
|
int "Location of RedBoot partition table"
|
|
|
|
default "-1"
|
|
|
|
---help---
|
|
|
|
This option is the Linux counterpart to the
|
|
|
|
CYGNUM_REDBOOT_FIS_DIRECTORY_BLOCK RedBoot compile time
|
|
|
|
option.
|
|
|
|
|
|
|
|
The option specifies which Flash sectors holds the RedBoot
|
2006-05-12 10:35:02 -06:00
|
|
|
partition table. A zero or positive value gives an absolute
|
2005-04-16 16:20:36 -06:00
|
|
|
erase block number. A negative value specifies a number of
|
|
|
|
sectors before the end of the device.
|
2005-11-07 04:15:26 -07:00
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
For example "2" means block number 2, "-1" means the last
|
|
|
|
block and "-2" means the penultimate block.
|
2005-11-07 04:15:26 -07:00
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
config MTD_REDBOOT_PARTS_UNALLOCATED
|
2006-06-08 23:12:49 -06:00
|
|
|
bool "Include unallocated flash regions"
|
2005-04-16 16:20:36 -06:00
|
|
|
help
|
|
|
|
If you need to register each unallocated flash region as a MTD
|
|
|
|
'partition', enable this option.
|
|
|
|
|
|
|
|
config MTD_REDBOOT_PARTS_READONLY
|
2006-06-08 23:12:49 -06:00
|
|
|
bool "Force read-only for RedBoot system images"
|
2005-04-16 16:20:36 -06:00
|
|
|
help
|
|
|
|
If you need to force read-only for 'RedBoot', 'RedBoot Config' and
|
|
|
|
'FIS directory' images, enable this option.
|
|
|
|
|
2010-10-30 00:35:02 -06:00
|
|
|
endif # MTD_REDBOOT_PARTS
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
config MTD_CMDLINE_PARTS
|
2013-01-15 18:12:49 -07:00
|
|
|
tristate "Command line partition table parsing"
|
|
|
|
depends on MTD
|
2005-04-16 16:20:36 -06:00
|
|
|
---help---
|
2006-05-12 10:35:02 -06:00
|
|
|
Allow generic configuration of the MTD partition tables via the kernel
|
2005-04-16 16:20:36 -06:00
|
|
|
command line. Multiple flash resources are supported for hardware where
|
2005-11-07 04:15:26 -07:00
|
|
|
different kinds of flash memory are available.
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
You will still need the parsing functions to be called by the driver
|
2005-11-07 04:15:26 -07:00
|
|
|
for your particular device. It won't happen automatically. The
|
|
|
|
SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for
|
2005-04-16 16:20:36 -06:00
|
|
|
example.
|
|
|
|
|
|
|
|
The format for the command line is as follows:
|
|
|
|
|
|
|
|
mtdparts=<mtddef>[;<mtddef]
|
|
|
|
<mtddef> := <mtd-id>:<partdef>[,<partdef>]
|
|
|
|
<partdef> := <size>[@offset][<name>][ro]
|
|
|
|
<mtd-id> := unique id used in mapping driver/device
|
2005-11-07 04:15:26 -07:00
|
|
|
<size> := standard linux memsize OR "-" to denote all
|
2005-04-16 16:20:36 -06:00
|
|
|
remaining space
|
|
|
|
<name> := (NAME)
|
|
|
|
|
2005-11-07 04:15:26 -07:00
|
|
|
Due to the way Linux handles the command line, no spaces are
|
|
|
|
allowed in the partition definition, including mtd id's and partition
|
2005-04-16 16:20:36 -06:00
|
|
|
names.
|
|
|
|
|
|
|
|
Examples:
|
|
|
|
|
|
|
|
1 flash resource (mtd-id "sa1100"), with 1 single writable partition:
|
|
|
|
mtdparts=sa1100:-
|
|
|
|
|
|
|
|
Same flash, but 2 named partitions, the first one being read-only:
|
|
|
|
mtdparts=sa1100:256k(ARMboot)ro,-(root)
|
|
|
|
|
|
|
|
If unsure, say 'N'.
|
|
|
|
|
|
|
|
config MTD_AFS_PARTS
|
|
|
|
tristate "ARM Firmware Suite partition parsing"
|
2010-10-30 00:35:02 -06:00
|
|
|
depends on ARM
|
2005-04-16 16:20:36 -06:00
|
|
|
---help---
|
|
|
|
The ARM Firmware Suite allows the user to divide flash devices into
|
|
|
|
multiple 'images'. Each such image has a header containing its name
|
|
|
|
and offset/size etc.
|
|
|
|
|
|
|
|
If you need code which can detect and parse these tables, and
|
|
|
|
register MTD 'partitions' corresponding to each image detected,
|
|
|
|
enable this option.
|
|
|
|
|
|
|
|
You will still need the parsing functions to be called by the driver
|
|
|
|
for your particular device. It won't happen automatically. The
|
2011-05-18 03:51:54 -06:00
|
|
|
'physmap' map driver (CONFIG_MTD_PHYSMAP) does this, for example.
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2008-01-15 16:54:43 -07:00
|
|
|
config MTD_OF_PARTS
|
2011-06-26 15:02:59 -06:00
|
|
|
tristate "OpenFirmware partitioning information support"
|
2012-05-17 14:43:09 -06:00
|
|
|
default y
|
2010-10-30 00:35:02 -06:00
|
|
|
depends on OF
|
2008-01-15 16:54:43 -07:00
|
|
|
help
|
|
|
|
This provides a partition parsing function which derives
|
|
|
|
the partition map from the children of the flash node,
|
2011-08-14 18:02:26 -06:00
|
|
|
as described in Documentation/devicetree/booting-without-of.txt.
|
2008-01-15 16:54:43 -07:00
|
|
|
|
2008-03-11 19:25:06 -06:00
|
|
|
config MTD_AR7_PARTS
|
|
|
|
tristate "TI AR7 partitioning support"
|
|
|
|
---help---
|
|
|
|
TI AR7 partitioning support
|
|
|
|
|
2011-12-05 08:08:08 -07:00
|
|
|
config MTD_BCM63XX_PARTS
|
|
|
|
tristate "BCM63XX CFE partitioning support"
|
|
|
|
depends on BCM63XX
|
|
|
|
select CRC32
|
|
|
|
help
|
|
|
|
This provides partions parsing for BCM63xx devices with CFE
|
|
|
|
bootloaders.
|
|
|
|
|
2012-08-29 23:41:16 -06:00
|
|
|
config MTD_BCM47XX_PARTS
|
|
|
|
tristate "BCM47XX partitioning support"
|
|
|
|
depends on BCM47XX
|
|
|
|
help
|
|
|
|
This provides partitions parser for devices based on BCM47xx
|
|
|
|
boards.
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
comment "User Modules And Translation Layers"
|
|
|
|
|
|
|
|
config MTD_CHAR
|
|
|
|
tristate "Direct char device access to MTD devices"
|
|
|
|
help
|
|
|
|
This provides a character device for each MTD device present in
|
|
|
|
the system, allowing the user to read and write directly to the
|
|
|
|
memory chips, and also use ioctl() to obtain information about
|
|
|
|
the device, or to erase parts of it.
|
|
|
|
|
2008-07-30 13:35:05 -06:00
|
|
|
config HAVE_MTD_OTP
|
|
|
|
bool
|
|
|
|
help
|
|
|
|
Enable access to OTP regions using MTD_CHAR.
|
|
|
|
|
2006-11-20 19:15:36 -07:00
|
|
|
config MTD_BLKDEVS
|
|
|
|
tristate "Common interface to block layer for MTD 'translation layers'"
|
2007-04-19 15:21:41 -06:00
|
|
|
depends on BLOCK
|
2006-11-20 19:15:36 -07:00
|
|
|
default n
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
config MTD_BLOCK
|
|
|
|
tristate "Caching block device access to MTD devices"
|
2007-04-19 15:21:41 -06:00
|
|
|
depends on BLOCK
|
2006-11-20 19:15:36 -07:00
|
|
|
select MTD_BLKDEVS
|
2005-04-16 16:20:36 -06:00
|
|
|
---help---
|
|
|
|
Although most flash chips have an erase size too large to be useful
|
|
|
|
as block devices, it is possible to use MTD devices which are based
|
|
|
|
on RAM chips in this manner. This block device is a user of MTD
|
|
|
|
devices performing that function.
|
|
|
|
|
|
|
|
At the moment, it is also required for the Journalling Flash File
|
|
|
|
System(s) to obtain a handle on the MTD device when it's mounted
|
|
|
|
(although JFFS and JFFS2 don't actually use any of the functionality
|
|
|
|
of the mtdblock device).
|
|
|
|
|
|
|
|
Later, it may be extended to perform read/erase/modify/write cycles
|
|
|
|
on flash chips to emulate a smaller block size. Needless to say,
|
|
|
|
this is very unsafe, but could be useful for file systems which are
|
|
|
|
almost never written to.
|
|
|
|
|
|
|
|
You do not need this option for use with the DiskOnChip devices. For
|
|
|
|
those, enable NFTL support (CONFIG_NFTL) instead.
|
|
|
|
|
|
|
|
config MTD_BLOCK_RO
|
|
|
|
tristate "Readonly block device access to MTD devices"
|
2007-04-19 15:21:41 -06:00
|
|
|
depends on MTD_BLOCK!=y && BLOCK
|
2006-11-20 19:15:36 -07:00
|
|
|
select MTD_BLKDEVS
|
2005-04-16 16:20:36 -06:00
|
|
|
help
|
|
|
|
This allows you to mount read-only file systems (such as cramfs)
|
|
|
|
from an MTD device, without the overhead (and danger) of the caching
|
|
|
|
driver.
|
|
|
|
|
|
|
|
You do not need this option for use with the DiskOnChip devices. For
|
|
|
|
those, enable NFTL support (CONFIG_NFTL) instead.
|
|
|
|
|
|
|
|
config FTL
|
|
|
|
tristate "FTL (Flash Translation Layer) support"
|
2007-04-19 15:21:41 -06:00
|
|
|
depends on BLOCK
|
2006-11-20 19:15:36 -07:00
|
|
|
select MTD_BLKDEVS
|
2005-04-16 16:20:36 -06:00
|
|
|
---help---
|
|
|
|
This provides support for the original Flash Translation Layer which
|
|
|
|
is part of the PCMCIA specification. It uses a kind of pseudo-
|
|
|
|
file system on a flash device to emulate a block device with
|
|
|
|
512-byte sectors, on top of which you put a 'normal' file system.
|
|
|
|
|
|
|
|
You may find that the algorithms used in this code are patented
|
|
|
|
unless you live in the Free World where software patents aren't
|
|
|
|
legal - in the USA you are only permitted to use this on PCMCIA
|
|
|
|
hardware, although under the terms of the GPL you're obviously
|
|
|
|
permitted to copy, modify and distribute the code as you wish. Just
|
|
|
|
not use it.
|
|
|
|
|
|
|
|
config NFTL
|
|
|
|
tristate "NFTL (NAND Flash Translation Layer) support"
|
2007-04-19 15:21:41 -06:00
|
|
|
depends on BLOCK
|
2006-11-20 19:15:36 -07:00
|
|
|
select MTD_BLKDEVS
|
2005-04-16 16:20:36 -06:00
|
|
|
---help---
|
|
|
|
This provides support for the NAND Flash Translation Layer which is
|
|
|
|
used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-
|
|
|
|
file system on a flash device to emulate a block device with
|
|
|
|
512-byte sectors, on top of which you put a 'normal' file system.
|
|
|
|
|
|
|
|
You may find that the algorithms used in this code are patented
|
|
|
|
unless you live in the Free World where software patents aren't
|
|
|
|
legal - in the USA you are only permitted to use this on DiskOnChip
|
|
|
|
hardware, although under the terms of the GPL you're obviously
|
|
|
|
permitted to copy, modify and distribute the code as you wish. Just
|
|
|
|
not use it.
|
|
|
|
|
|
|
|
config NFTL_RW
|
|
|
|
bool "Write support for NFTL"
|
|
|
|
depends on NFTL
|
|
|
|
help
|
|
|
|
Support for writing to the NAND Flash Translation Layer, as used
|
|
|
|
on the DiskOnChip.
|
|
|
|
|
|
|
|
config INFTL
|
|
|
|
tristate "INFTL (Inverse NAND Flash Translation Layer) support"
|
2007-04-19 15:21:41 -06:00
|
|
|
depends on BLOCK
|
2006-11-20 19:15:36 -07:00
|
|
|
select MTD_BLKDEVS
|
2005-04-16 16:20:36 -06:00
|
|
|
---help---
|
2005-11-07 04:15:26 -07:00
|
|
|
This provides support for the Inverse NAND Flash Translation
|
2005-04-16 16:20:36 -06:00
|
|
|
Layer which is used on M-Systems' newer DiskOnChip devices. It
|
|
|
|
uses a kind of pseudo-file system on a flash device to emulate
|
|
|
|
a block device with 512-byte sectors, on top of which you put
|
|
|
|
a 'normal' file system.
|
|
|
|
|
|
|
|
You may find that the algorithms used in this code are patented
|
|
|
|
unless you live in the Free World where software patents aren't
|
|
|
|
legal - in the USA you are only permitted to use this on DiskOnChip
|
|
|
|
hardware, although under the terms of the GPL you're obviously
|
|
|
|
permitted to copy, modify and distribute the code as you wish. Just
|
|
|
|
not use it.
|
|
|
|
|
2005-06-16 02:49:33 -06:00
|
|
|
config RFD_FTL
|
|
|
|
tristate "Resident Flash Disk (Flash Translation Layer) support"
|
2007-04-19 15:21:41 -06:00
|
|
|
depends on BLOCK
|
2006-11-20 19:15:36 -07:00
|
|
|
select MTD_BLKDEVS
|
2005-06-16 02:49:33 -06:00
|
|
|
---help---
|
2005-11-07 04:15:26 -07:00
|
|
|
This provides support for the flash translation layer known
|
|
|
|
as the Resident Flash Disk (RFD), as used by the Embedded BIOS
|
2005-07-11 04:41:53 -06:00
|
|
|
of General Software. There is a blurb at:
|
|
|
|
|
|
|
|
http://www.gensw.com/pages/prod/bios/rfd.htm
|
2005-06-16 02:49:33 -06:00
|
|
|
|
2006-09-22 04:01:37 -06:00
|
|
|
config SSFDC
|
2006-09-23 03:24:36 -06:00
|
|
|
tristate "NAND SSFDC (SmartMedia) read only translation layer"
|
2007-04-19 15:21:41 -06:00
|
|
|
depends on BLOCK
|
2006-11-20 19:15:36 -07:00
|
|
|
select MTD_BLKDEVS
|
2006-09-22 04:01:37 -06:00
|
|
|
help
|
|
|
|
This enables read only access to SmartMedia formatted NAND
|
|
|
|
flash. You can mount it with FAT file system.
|
|
|
|
|
2010-02-22 11:39:41 -07:00
|
|
|
|
|
|
|
config SM_FTL
|
|
|
|
tristate "SmartMedia/xD new translation layer"
|
2012-10-02 12:17:47 -06:00
|
|
|
depends on BLOCK
|
2010-02-22 11:39:41 -07:00
|
|
|
select MTD_BLKDEVS
|
2010-03-19 09:22:54 -06:00
|
|
|
select MTD_NAND_ECC
|
2010-02-22 11:39:41 -07:00
|
|
|
help
|
2010-07-28 09:53:17 -06:00
|
|
|
This enables EXPERIMENTAL R/W support for SmartMedia/xD
|
2010-03-08 19:45:00 -07:00
|
|
|
FTL (Flash translation layer).
|
2010-07-28 09:53:17 -06:00
|
|
|
Write support is only lightly tested, therefore this driver
|
|
|
|
isn't recommended to use with valuable data (anyway if you have
|
|
|
|
valuable data, do backups regardless of software/hardware you
|
|
|
|
use, because you never know what will eat your data...)
|
|
|
|
If you only need R/O access, you can use older R/O driver
|
|
|
|
(CONFIG_SSFDC)
|
2010-02-22 11:39:41 -07:00
|
|
|
|
2007-05-29 06:31:42 -06:00
|
|
|
config MTD_OOPS
|
|
|
|
tristate "Log panic/oops to an MTD buffer"
|
|
|
|
help
|
|
|
|
This enables panic and oops messages to be logged to a circular
|
|
|
|
buffer in a flash partition where it can be read back at some
|
|
|
|
later point.
|
|
|
|
|
2011-02-14 07:16:11 -07:00
|
|
|
config MTD_SWAP
|
|
|
|
tristate "Swap on MTD device support"
|
|
|
|
depends on MTD && SWAP
|
|
|
|
select MTD_BLKDEVS
|
|
|
|
help
|
|
|
|
Provides volatile block device driver on top of mtd partition
|
|
|
|
suitable for swapping. The mapping of written blocks is not saved.
|
|
|
|
The driver provides wear leveling by storing erase counter into the
|
|
|
|
OOB.
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
source "drivers/mtd/chips/Kconfig"
|
|
|
|
|
|
|
|
source "drivers/mtd/maps/Kconfig"
|
|
|
|
|
|
|
|
source "drivers/mtd/devices/Kconfig"
|
|
|
|
|
|
|
|
source "drivers/mtd/nand/Kconfig"
|
|
|
|
|
2005-07-11 04:41:53 -06:00
|
|
|
source "drivers/mtd/onenand/Kconfig"
|
|
|
|
|
2008-12-16 11:24:14 -07:00
|
|
|
source "drivers/mtd/lpddr/Kconfig"
|
|
|
|
|
UBI: Unsorted Block Images
UBI (Latin: "where?") manages multiple logical volumes on a single
flash device, specifically supporting NAND flash devices. UBI provides
a flexible partitioning concept which still allows for wear-levelling
across the whole flash device.
In a sense, UBI may be compared to the Logical Volume Manager
(LVM). Whereas LVM maps logical sector numbers to physical HDD sector
numbers, UBI maps logical eraseblocks to physical eraseblocks.
More information may be found at
http://www.linux-mtd.infradead.org/doc/ubi.html
Partitioning/Re-partitioning
An UBI volume occupies a certain number of erase blocks. This is
limited by a configured maximum volume size, which could also be
viewed as the partition size. Each individual UBI volume's size can
be changed independently of the other UBI volumes, provided that the
sum of all volume sizes doesn't exceed a certain limit.
UBI supports dynamic volumes and static volumes. Static volumes are
read-only and their contents are protected by CRC check sums.
Bad eraseblocks handling
UBI transparently handles bad eraseblocks. When a physical
eraseblock becomes bad, it is substituted by a good physical
eraseblock, and the user does not even notice this.
Scrubbing
On a NAND flash bit flips can occur on any write operation,
sometimes also on read. If bit flips persist on the device, at first
they can still be corrected by ECC, but once they accumulate,
correction will become impossible. Thus it is best to actively scrub
the affected eraseblock, by first copying it to a free eraseblock
and then erasing the original. The UBI layer performs this type of
scrubbing under the covers, transparently to the UBI volume users.
Erase Counts
UBI maintains an erase count header per eraseblock. This frees
higher-level layers (like file systems) from doing this and allows
for centralized erase count management instead. The erase counts are
used by the wear-levelling algorithm in the UBI layer. The algorithm
itself is exchangeable.
Booting from NAND
For booting directly from NAND flash the hardware must at least be
capable of fetching and executing a small portion of the NAND
flash. Some NAND flash controllers have this kind of support. They
usually limit the window to a few kilobytes in erase block 0. This
"initial program loader" (IPL) must then contain sufficient logic to
load and execute the next boot phase.
Due to bad eraseblocks, which may be randomly scattered over the
flash device, it is problematic to store the "secondary program
loader" (SPL) statically. Also, due to bit-flips it may become
corrupted over time. UBI allows to solve this problem gracefully by
storing the SPL in a small static UBI volume.
UBI volumes vs. static partitions
UBI volumes are still very similar to static MTD partitions:
* both consist of eraseblocks (logical eraseblocks in case of UBI
volumes, and physical eraseblocks in case of static partitions;
* both support three basic operations - read, write, erase.
But UBI volumes have the following advantages over traditional
static MTD partitions:
* there are no eraseblock wear-leveling constraints in case of UBI
volumes, so the user should not care about this;
* there are no bit-flips and bad eraseblocks in case of UBI volumes.
So, UBI volumes may be considered as flash devices with relaxed
restrictions.
Where can it be found?
Documentation, kernel code and applications can be found in the MTD
gits.
What are the applications for?
The applications help to create binary flash images for two purposes: pfi
files (partial flash images) for in-system update of UBI volumes, and plain
binary images, with or without OOB data in case of NAND, for a manufacturing
step. Furthermore some tools are/and will be created that allow flash content
analysis after a system has crashed..
Who did UBI?
The original ideas, where UBI is based on, were developed by Andreas
Arnez, Frank Haverkamp and Thomas Gleixner. Josh W. Boyer and some others
were involved too. The implementation of the kernel layer was done by Artem
B. Bityutskiy. The user-space applications and tools were written by Oliver
Lohmann with contributions from Frank Haverkamp, Andreas Arnez, and Artem.
Joern Engel contributed a patch which modifies JFFS2 so that it can be run on
a UBI volume. Thomas Gleixner did modifications to the NAND layer. Alexander
Schmidt made some testing work as well as core functionality improvements.
Signed-off-by: Artem B. Bityutskiy <dedekind@linutronix.de>
Signed-off-by: Frank Haverkamp <haver@vnet.ibm.com>
2006-06-27 02:22:22 -06:00
|
|
|
source "drivers/mtd/ubi/Kconfig"
|
|
|
|
|
2007-04-19 15:21:41 -06:00
|
|
|
endif # MTD
|