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>
This commit is contained in:

committed by
Artem Bityutskiy

parent
518ceef0c9
commit
2ba3d76a1e
@@ -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
|
||||
|
Reference in New Issue
Block a user