mtd/drivers/mtd Config.in,1.74,1.75 Kconfig,1.1,1.2 Makefile.common,1.1,1.2

David Woodhouse dwmw2 at infradead.org
Fri May 23 07:38:32 EDT 2003


Update of /home/cvs/mtd/drivers/mtd
In directory phoenix.infradead.org:/tmp/cvs-serv22538/drivers/mtd

Modified Files:
	Config.in Kconfig Makefile.common 
Log Message:
Makefile and config bits for INFTL

Index: Config.in
===================================================================
RCS file: /home/cvs/mtd/drivers/mtd/Config.in,v
retrieving revision 1.74
retrieving revision 1.75
diff -u -r1.74 -r1.75
--- Config.in	23 Apr 2002 13:52:14 -0000	1.74
+++ Config.in	23 May 2003 11:38:29 -0000	1.75
@@ -30,6 +30,7 @@
    if [ "$CONFIG_NFTL" = "y" -o "$CONFIG_NFTL" = "m" ]; then
       bool '    Write support for NFTL (BETA)' CONFIG_NFTL_RW
    fi
+   dep_tristate '  INFTL (Inverse NAND Flash Translation Layer) support' CONFIG_INFTL $CONFIG_MTD
 
    source drivers/mtd/chips/Config.in
 

Index: Kconfig
===================================================================
RCS file: /home/cvs/mtd/drivers/mtd/Kconfig,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Kconfig	26 Nov 2002 22:29:08 -0000	1.1
+++ Kconfig	23 May 2003 11:38:29 -0000	1.2
@@ -207,6 +207,23 @@
 	  <linux-mtd at lists.infradead.org> if you want to help to make it more
 	  reliable.
 
+config INFTL
+	tristate "INFTL (Inverse NAND Flash Translation Layer) support"
+	depends on MTD
+	---help---
+	  This provides support for the Inverse NAND Flash Translation 
+	  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.
+
 source "drivers/mtd/chips/Kconfig"
 
 source "drivers/mtd/maps/Kconfig"

Index: Makefile.common
===================================================================
RCS file: /home/cvs/mtd/drivers/mtd/Makefile.common,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Makefile.common	21 May 2003 15:00:00 -0000	1.1
+++ Makefile.common	23 May 2003 11:38:29 -0000	1.2
@@ -33,8 +33,10 @@
 obj-$(CONFIG_MTD_BLOCK_RO)	+= mtdblock_ro.o mtd_blkdevs.o
 obj-$(CONFIG_FTL)		+= ftl.o mtd_blkdevs.o
 obj-$(CONFIG_NFTL)		+= nftl.o mtd_blkdevs.o
+obj-$(CONFIG_INFTL)		+= inftl.o mtd_blkdevs.o
 
 nftl-objs		:= nftlcore.o nftlmount.o
+inftl-objs		:= inftlcore.o inftlmount.o
 
 ifeq ($(PATCHLEVEL),4)
 
@@ -48,7 +50,7 @@
 
 O_TARGET	:= mtdlink.o
 
-list-multi	:= nftl.o mtd_blkdevs.o
+list-multi	:= nftl.o inftl.o mtd_blkdevs.o
 
 mod-subdirs	:= 
 subdir-y	:= chips maps devices nand
@@ -58,6 +60,9 @@
 
 nftl.o: $(nftl-objs)
 	$(LD) -r -o $@ $(nftl-objs)
+
+inftl.o: $(inftl-objs)
+	$(LD) -r -o $@ $(inftl-objs)
 
 mtd_blkdevs.o: $(mtd_blkdevs-objs)
 	$(LD) -r -o $@ $(mtd_blkdevs-objs)




More information about the linux-mtd-cvs mailing list