diff options
| author | Dmitry Pervushin <dpervushin@embeddedalley.com> | 2009-05-31 18:32:59 +0400 |
|---|---|---|
| committer | Artem Bityutskiy <Artem.Bityutskiy@nokia.com> | 2009-06-03 17:45:23 +0300 |
| commit | 2ba3d76a1e29f2ba64fbc762875cf9fb2d4ba2ba (patch) | |
| tree | 633d48cb740534827b2a764c74e7b423415c0774 /drivers/mtd/ubi/Kconfig | |
| parent | 518ceef0c9ca97023e45ae46aedaefa240c690a6 (diff) | |
| download | kernel_samsung_smdk4412-2ba3d76a1e29f2ba64fbc762875cf9fb2d4ba2ba.tar.gz kernel_samsung_smdk4412-2ba3d76a1e29f2ba64fbc762875cf9fb2d4ba2ba.tar.bz2 kernel_samsung_smdk4412-2ba3d76a1e29f2ba64fbc762875cf9fb2d4ba2ba.zip | |
UBI: make gluebi a separate module
[Artem: re-worked the patch: made it release resources when the
module is unloaded, made it do module referencing, made it really
independent on UBI, tested it with the UBI test-suite which can
be found in ubi-2.6.git/tests/ubi-tests, re-named most of the
funcs/variables to get rid of the "ubi" word and make names
consistent.]
Signed-off-by: Dmitry Pervushin <dpervushin@embeddedalley.com>
Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Diffstat (limited to 'drivers/mtd/ubi/Kconfig')
| -rw-r--r-- | drivers/mtd/ubi/Kconfig | 13 |
1 files changed, 7 insertions, 6 deletions
diff --git a/drivers/mtd/ubi/Kconfig b/drivers/mtd/ubi/Kconfig index 3f063108e95..b1cd7a1a219 100644 --- a/drivers/mtd/ubi/Kconfig +++ b/drivers/mtd/ubi/Kconfig @@ -49,15 +49,16 @@ config MTD_UBI_BEB_RESERVE reserved. Leave the default value if unsure. config MTD_UBI_GLUEBI - bool "Emulate MTD devices" + tristate "MTD devices emulation driver (gluebi)" default n depends on MTD_UBI help - This option enables MTD devices emulation on top of UBI volumes: for - each UBI volumes an MTD device is created, and all I/O to this MTD - device is redirected to the UBI volume. This is handy to make - MTD-oriented software (like JFFS2) work on top of UBI. Do not enable - this if no legacy software will be used. + This option enables gluebi - an additional driver which emulates MTD + devices on top of UBI volumes: for each UBI volumes an MTD device is + created, and all I/O to this MTD device is redirected to the UBI + volume. This is handy to make MTD-oriented software (like JFFS2) + work on top of UBI. Do not enable this unless you use legacy + software. source "drivers/mtd/ubi/Kconfig.debug" endmenu |